Triple
T4970214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuyang |
E111629
|
entity |
| Predicate | majorRailwayJunctionFor |
P14468
|
FINISHED |
| Object | central China |
—
|
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 China | Statement: [Fuyang, majorRailwayJunctionFor, central China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRailwayJunctionFor Context triple: [Fuyang, majorRailwayJunctionFor, central China]
-
A.
railwayJunctionFor
chosen
Indicates that a location serves as a junction point where multiple railway lines or routes connect or intersect for a given railway network or service.
-
B.
transportationJunctionFor
Indicates a location that serves as a connecting point where multiple transportation routes or modes meet, intersect, or transfer.
-
C.
railroadTerminusFor
Indicates that one location serves as the end point or final station of a particular railroad line for another location.
-
D.
hasMajorRailLinksTo
Indicates that there are significant railway connections or routes between two locations.
-
E.
interchangeStation
Indicates a station where passengers can transfer between different routes, lines, or modes of transportation.
- 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_69bd441a0eb481908050fa4273b19eae |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd7146e6e881908a55ab2756b631f6 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:33 p.m.