Triple
T7782692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baoji |
E221560
|
entity |
| Predicate | roadHubRole |
P25845
|
FINISHED |
| Object | junction for national expressways in Northwest 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: junction for national expressways in Northwest China | Statement: [Baoji, roadHubRole, junction for national expressways in Northwest China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadHubRole Context triple: [Baoji, roadHubRole, junction for national expressways in Northwest China]
-
A.
roadSystemRole
chosen
Indicates the specific functional role or responsibility an entity has within a road or transportation network system.
-
B.
transportationRole
Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
-
C.
mobilityRole
Indicates the functional role or capacity an entity has in enabling, supporting, or performing movement or transportation.
-
D.
roleInAmazon
Indicates that one entity holds a specific role, position, or function within Amazon in relation to the other entity.
-
E.
roleInEngine
Indicates the specific function or responsibility an entity has within an engine or engine-like system.
- 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_69ca83ebbef881909ac47f789145fef7 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cae7e779ec8190b77296d9c2ac3210 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
Created at: March 30, 2026, 4:22 p.m.