Triple
T23022895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Töv Province |
E573214
|
entity |
| Predicate | railNetworkHubFor |
P64887
|
FINISHED |
| Object | central Mongolia |
—
|
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: central Mongolia | Statement: [Töv Province, railNetworkHubFor, central Mongolia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railNetworkHubFor Context triple: [Töv Province, railNetworkHubFor, central Mongolia]
-
A.
railNetworkCenter
chosen
Indicates that a location functions as a central hub or focal point within a rail transportation network.
-
B.
railwayConnectsTo
Indicates that one railway line, track, or network is directly linked or joined to another, allowing trains to move between them.
-
C.
railroadTerminusFor
Indicates that one location serves as the end point or final station of a particular railroad line for another location.
-
D.
isRailwayStationInNetwork
Indicates that a railway station belongs to, and is served as part of, a particular railway network.
-
E.
transportationHubType
Indicates the specific kind of transportation hub an entity is (e.g., airport, train station, bus terminal).
- 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183ea23088190b2f42d9bf01514ac |
completed | April 29, 2026, 4:07 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:52 p.m.