Triple
T30795168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge road network |
E784209
|
entity |
| Predicate | hasRingRoadElement |
P180971
|
FINISHED |
| Object | A1134 road |
—
|
NE NERFINISHED |
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: A1134 road | Statement: [Cambridge road network, hasRingRoadElement, A1134 road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRingRoadElement Context triple: [Cambridge road network, hasRingRoadElement, A1134 road]
-
A.
hasRingRoadType
Indicates that an entity is associated with a specific type or classification of ring road.
-
B.
hasRingRoadRole
Indicates that an entity has a specific functional role or responsibility in relation to a ring road.
-
C.
hasRingRoadLengthApproxKm
Indicates that an entity has a ring road whose length is approximately a specified number of kilometers.
-
D.
hasLoopRoad
Indicates that a location or area is connected by a road that forms a closed loop, beginning and ending at the same point.
-
E.
isWithinRingRoad
Indicates that one location lies inside the area enclosed by a specified ring road.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 29, 2026, 8:42 p.m.