Triple
T2434606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tianmen |
E52925
|
entity |
| Predicate | roadTransport |
P12181
|
FINISHED |
| Object | connected to regional highway 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: connected to regional highway network | Statement: [Tianmen, roadTransport, connected to regional highway network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadTransport Context triple: [Tianmen, roadTransport, connected to regional highway network]
-
A.
transportation
Indicates the movement of someone or something from one place to another, typically using a vehicle or transit system.
-
B.
transportationContext
Indicates the situational or environmental conditions under which transportation occurs, such as mode, purpose, or circumstances of travel.
-
C.
transportNetwork
chosen
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
-
D.
transports
Indicates that one entity carries or conveys another entity from one place to another.
-
E.
roadUse
Indicates that an entity utilizes or travels on a particular road or roadway for movement or transport.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcebf7cac8190889e6890d72c256c |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5ac11b081908ce6a506e81a742a |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.