Triple
T4810447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dodoma |
E107054
|
entity |
| Predicate | railwayOriginRole |
P26273
|
FINISHED |
| Object | railway station town on the Central Line |
—
|
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: railway station town on the Central Line | Statement: [Dodoma, railwayOriginRole, railway station town on the Central Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayOriginRole Context triple: [Dodoma, railwayOriginRole, railway station town on the Central Line]
-
A.
railwayLineRole
Indicates the specific functional role or purpose that a railway line serves within a rail network or transportation system.
-
B.
railNetworkRole
Indicates the specific function or responsibility an entity has within a rail network system.
-
C.
hasRollingStockOrigin
Indicates that a piece of rolling stock originates from, or was initially based in, a particular location or source.
-
D.
railLineOrigin
chosen
Indicates that a rail line begins or originates from a specified location or point.
-
E.
railwayControlledBy
Indicates that the operation, management, or authority over a railway is exercised by a specified controlling 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_69bd43f779448190b92885cb70abb6c2 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1c43a48190a65e56b1624a2339 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:23 p.m.