Triple
T6390197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baoding |
E143804
|
entity |
| Predicate | isRegionalTransportationHub |
P2413
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Baoding, isRegionalTransportationHub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegionalTransportationHub Context triple: [Baoding, isRegionalTransportationHub, true]
-
A.
hasTransportHub
chosen
Indicates that a location contains or serves as a central facility where multiple transport routes or modes connect for passenger or cargo movement.
-
B.
isTransportationHubCodeFor
Indicates that a given code uniquely identifies and represents a specific transportation hub, such as a station, airport, or terminal.
-
C.
isTransportHubBetween
Indicates that a location functions as a central node facilitating transportation connections between two or more other places.
-
D.
hasMajorRailLinksTo
Indicates that there are significant railway connections or routes between two locations.
-
E.
hasMajorTransportationRole
Indicates that an entity plays a primary or significant role in providing or supporting transportation services or infrastructure.
- 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_69c008db906c819096f3597d55d95432 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0686cc6d481909c62a29a84a4ce8e |
completed | March 22, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69c060eff524819094cee1c70a0c1ff4 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:34 p.m.