Triple
T14664794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bamako–Dakar Railway |
E344338
|
entity |
| Predicate | typeOfLine |
P14639
|
FINISHED |
| Object | intercity rail 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: intercity rail line | Statement: [Bamako–Dakar Railway, typeOfLine, intercity rail line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLine Context triple: [Bamako–Dakar Railway, typeOfLine, intercity rail line]
-
A.
lineType
Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
-
B.
servedLineType
Indicates the type or category of service line associated with or provided in a given context.
-
C.
servesLineType
Indicates that a service or entity operates or supports a specific type or category of line (e.g., transport, communication, or utility line).
-
D.
railwayLineType
chosen
Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
-
E.
servedByLineType
Indicates that a service, stop, or route is operated or covered by a specific type of transit line.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb54c69f8819080a37161deecfba8 |
completed | April 14, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.