Triple
T24771767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antlers |
E619743
|
entity |
| Predicate | featuresMythicCreature |
P45276
|
FINISHED |
| Object | Wendigo |
—
|
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: Wendigo | Statement: [Antlers, featuresMythicCreature, Wendigo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresMythicCreature Context triple: [Antlers, featuresMythicCreature, Wendigo]
-
A.
featuresCreatureOrLegend
Indicates that something includes, depicts, or prominently involves a particular creature or legendary being.
-
B.
featuresMythicalObject
Indicates that something includes, presents, or prominently involves a mythical or legendary object.
-
C.
featuresMonster
Indicates that something includes or prominently presents a monster as part of its content or composition.
-
D.
hasMythologicalFeature
chosen
Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
-
E.
monsterCharacteristic
Indicates that a monster possesses a particular attribute, trait, or quality.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 18, 2026, 4:31 a.m.