Triple
T26852271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanzanian railway network |
E676087
|
entity |
| Predicate | isKeyModeIn |
P165059
|
FINISHED |
| Object | Tanzania transport system |
—
|
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: Tanzania transport system | Statement: [Tanzanian railway network, isKeyModeIn, Tanzania transport system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyModeIn Context triple: [Tanzanian railway network, isKeyModeIn, Tanzania transport system]
-
A.
isInKey
Indicates that something is located within, or belongs to, a specified key or key-based grouping in a structured context.
-
B.
isKeyCharacterIn
Indicates that an entity plays a central or primary role as a main or significant character within another entity, such as a story, game, or narrative work.
-
C.
isKeyProcessIn
Indicates that a process plays a central or essential role within a larger system, workflow, or operation.
-
D.
isKeyStructureOn
Indicates that one entity serves as a primary or essential structural component located on or attached to another entity.
-
E.
isStandardKey
Indicates that a given key conforms to a defined standard or canonical set of keys within a system or context.
- 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 5:18 a.m.