Triple
T9948111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ant |
E195256
|
entity |
| Predicate | mentionsCreature |
P91311
|
FINISHED |
| Object | ant |
—
|
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: ant | Statement: [The Ant, mentionsCreature, ant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionsCreature Context triple: [The Ant, mentionsCreature, ant]
-
A.
usesCreature
Indicates that one entity employs, controls, or relies on a creature to perform an action or fulfill a function.
-
B.
hasCreature
Indicates that one entity possesses, contains, or is associated with a particular creature.
-
C.
hasAllegedCreature
Indicates that an entity is claimed or reported to possess, host, or be associated with a creature whose existence or nature is uncertain or disputed.
-
D.
associatedCreatureInSomeVersions
Indicates that one entity is linked to another entity as a related creature, but only in certain versions or variants of a work or source.
-
E.
featuresCreatureOrLegend
Indicates that something includes, depicts, or prominently involves a particular creature or legendary being.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb659307c81908279adb641ceef86 |
completed | April 2, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:45 p.m.