Triple
T26960015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Richmond railway station |
E679013
|
entity |
| Predicate | hasTrainConnections |
P71547
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [East Richmond railway station, hasTrainConnections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainConnections Context triple: [East Richmond railway station, hasTrainConnections, yes]
-
A.
hasPassengerRailConnection
chosen
Indicates that there exists a passenger rail service linking one location or transport node to another.
-
B.
providesRailConnectionsWithin
Indicates that an entity offers or facilitates rail transport links connecting locations inside a specified area or region.
-
C.
countryRailConnection
Indicates that there is a railway connection or service linking two countries.
-
D.
hasPlannedTransportConnection
Indicates that there is an intended or scheduled transport link (e.g., route, service, or connection) planned to operate between the related entities.
-
E.
hasNightTrainService
Indicates that a transportation route or station is served by trains that operate during nighttime hours.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 27, 2026, 6:30 a.m.