Triple
T30795176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge road network |
E784209
|
entity |
| Predicate | hasRadialRoute |
P72721
|
FINISHED |
| Object | Hills 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: Hills Road | Statement: [Cambridge road network, hasRadialRoute, Hills Road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRadialRoute Context triple: [Cambridge road network, hasRadialRoute, Hills Road]
-
A.
isRadialRouteOf
chosen
Indicates that one route functions as a radial connection extending outward from a central point, hub, or main route.
-
B.
hasRadialBehavior
Indicates that one entity exhibits behavior or properties that vary or extend outward from a central point relative to another entity or reference frame.
-
C.
hasRadialNodeCount
Indicates the number of radial nodes (radially arranged elements or divisions) associated with an entity.
-
D.
hasRouteNetwork
Indicates that one entity possesses, is associated with, or is covered by a specific route network connecting multiple locations or paths.
-
E.
isOnCircularRoute
Indicates that an entity follows or belongs to a route that forms a closed loop, starting and ending at the same point.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 29, 2026, 8:42 p.m.