Triple
T4138385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorylinae |
E89211
|
entity |
| Predicate | redefinedToInclude |
P9775
|
FINISHED |
| Object | all true army ants |
—
|
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: all true army ants | Statement: [Dorylinae, redefinedToInclude, all true army ants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redefinedToInclude Context triple: [Dorylinae, redefinedToInclude, all true army ants]
-
A.
renamedToInclude
Indicates that an entity has been renamed so that its new name explicitly includes another specified element (such as a term, identifier, or component).
-
B.
wasRedefinedIn
chosen
Indicates that an existing entity or concept was modified, updated, or given a new definition at a particular time or in a specific context.
-
C.
formerlyIncluded
Indicates that an entity was previously part of, contained in, or a member of another entity, but is no longer included.
-
D.
previouslyDefinedIn
Indicates that something has been defined or introduced earlier in time or in a prior context relative to the current reference point.
-
E.
includedWith
Indicates that one entity is provided or packaged together as part of 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.