Triple
T7053488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sector 3 |
E164026
|
entity |
| Predicate | hasRoadNetworkType |
P74765
|
FINISHED |
| Object | urban road 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: urban road network | Statement: [Sector 3, hasRoadNetworkType, urban road network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadNetworkType Context triple: [Sector 3, hasRoadNetworkType, urban road network]
-
A.
hasRoadNetworkQuality
Indicates the assessed level or condition of the road network associated with an entity.
-
B.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
C.
isPublicRoadNetwork
Indicates that a given road network is officially designated for public use and accessible to the general public for transportation.
-
D.
roadNetworkConformsTo
Indicates that a road network adheres to, or is compliant with, a specified standard, specification, or reference model.
-
E.
hasTunnelsOnRoad
Indicates that a road includes or passes through one or more tunnels along its route.
- F. None of above. chosen
Provenance (4 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_69c68861678881909961ddf4d779f750 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bdc1f08190975fcdbbb1854d1e |
completed | March 27, 2026, 7:59 p.m. |
| PDg | Predicate description generation | batch_69c6e4a15b088190bee9a23e94aaac53 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:37 p.m.