Triple
T37961678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mordecai |
E947021
|
entity |
| Predicate | classModType |
P192740
|
FINISHED |
| Object | Hunter class mods |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Hunter class mods | Statement: [Mordecai, classModType, Hunter class mods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classModType Context triple: [Mordecai, classModType, Hunter class mods]
-
A.
moduleType
Indicates the classification or category of a module in terms of its functional or structural type.
-
B.
modulusType
Indicates the type or category of modulus associated with an entity or operation (e.g., which modulus definition or scheme is being used).
-
C.
modeType
Indicates the specific manner, method, or operational mode in which an action, process, or system is carried out or functions.
-
D.
moduleOf
Indicates that one entity functions as a component or sub-unit that belongs to, or is contained within, another larger entity.
-
E.
methodModifier
Indicates that one entity specifies a modifier (such as visibility, static, abstract, etc.) that qualifies or constrains the behavior or declaration of a method represented by another entity.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
| PDg | Predicate description generation | batch_69fd28379d2c8190903ba228ee1cc756 |
completed | May 8, 2026, 12:03 a.m. |
Created at: May 3, 2026, 4:20 p.m.