Triple
T8684694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | March railway station |
E206128
|
entity |
| Predicate | railNetworkScope |
P24517
|
FINISHED |
| Object | regional rail network |
—
|
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: regional rail network | Statement: [March railway station, railNetworkScope, regional rail network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railNetworkScope Context triple: [March railway station, railNetworkScope, regional rail network]
-
A.
railroadNetwork
chosen
Indicates a relationship where locations are connected as part of the same system of railway lines and infrastructure used for train transport.
-
B.
railNetworkRole
Indicates the specific function or responsibility an entity has within a rail network system.
-
C.
railNetworkCenter
Indicates that a location functions as a central hub or focal point within a rail transportation network.
-
D.
railNetworkSide
Indicates on which side of a rail network (e.g., left or right relative to a reference direction) an entity is located or associated.
-
E.
railFranchise
Indicates a contractual relationship in which a company is granted the right to operate rail services or manage rail infrastructure within a specified area or route.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4aeae740819099093906ccc5f640 |
completed | March 31, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.