Triple
T38493056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lobatse–Ramatlabama line |
E918106
|
entity |
| Predicate | hasInlandStation |
P201282
|
FINISHED |
| Object | Lobatse railway station |
—
|
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: Lobatse railway station | Statement: [Lobatse–Ramatlabama line, hasInlandStation, Lobatse railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInlandStation Context triple: [Lobatse–Ramatlabama line, hasInlandStation, Lobatse railway station]
-
A.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
-
B.
hasStationAlong
chosen
Indicates that a route, line, or path includes a particular station located somewhere along its course.
-
C.
hasInterchangeStationWith
Indicates that two transportation lines, routes, or systems share a station where passengers can transfer between them.
-
D.
isStationOf
Indicates that a given location functions as a station (e.g., transport or service hub) associated with or serving a particular system, line, route, or organization.
-
E.
hasInlandCity
Indicates that one entity has, contains, or is associated with a city located inland (away from the coast or major bodies of water).
- 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a016777257081908841c5522dfa76e6 |
completed | May 11, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_6a0164e49bec8190af3c8626be9677a9 |
completed | May 11, 2026, 5:11 a.m. |
Created at: May 3, 2026, 4:31 p.m.