Triple
T25447336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EASTAFRICAN |
E637671
|
entity |
| Predicate | usedByPredecessorOf |
P163010
|
FINISHED |
| Object | Air Tanzania |
—
|
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: Air Tanzania | Statement: [EASTAFRICAN, usedByPredecessorOf, Air Tanzania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByPredecessorOf Context triple: [EASTAFRICAN, usedByPredecessorOf, Air Tanzania]
-
A.
usedByPredecessorOf
chosen
Indicates that something is used by an entity that is the predecessor of another entity in a sequence or hierarchy.
-
B.
predecessorUsedFrom
Indicates that something was used or derived from a preceding version, state, or entity that came before it.
-
C.
ownedByPredecessor
Indicates that something is or was owned by an entity that previously held a given role, position, or status before the current one.
-
D.
calledPredecessorOf
Indicates that one entity is referred to or designated as the predecessor of another entity.
-
E.
contributedToPredecessorOf
Indicates that one entity contributed to or influenced another entity that came before a specified successor in a sequence or lineage.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 2:02 p.m.