Triple
T37553482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legion |
E933641
|
entity |
| Predicate | newClass |
P100345
|
FINISHED |
| Object | Demon Hunter |
—
|
NE NERFINISHED |
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: Demon Hunter | Statement: [Legion, newClass, Demon Hunter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: newClass Context triple: [Legion, newClass, Demon Hunter]
-
A.
clase
Indicates a classification or type relationship, where one entity is categorized as belonging to a particular class or category defined by another entity.
-
B.
laterClass
Indicates that one class occurs or is scheduled at a time later than another class.
-
C.
designClass
Indicates that one entity is the design or blueprint class from which the other entity is derived or instantiated.
-
D.
classIntroduced
Indicates that a particular class (e.g., in a programming language or system) has been newly defined or made available within a given context or scope.
-
E.
addsClass
chosen
Indicates that one entity introduces or appends a class (such as a classification, type, or code) to another entity.
- F. None of above.
Provenance (3 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.