Triple
T27389701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chalk Farm Road |
E691487
|
entity |
| Predicate | hasConnectingJunctionWith |
P1018
|
FINISHED |
| Object | Camden High Street |
—
|
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: Camden High Street | Statement: [Chalk Farm Road, hasConnectingJunctionWith, Camden High Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectingJunctionWith Context triple: [Chalk Farm Road, hasConnectingJunctionWith, Camden High Street]
-
A.
hasJunctionWith
chosen
Indicates that one entity meets or intersects with another at a shared junction point.
-
B.
hasJunctionIn
Indicates that one entity contains or includes a junction located within the spatial or structural extent of another entity.
-
C.
isNumberedJunctionOf
Indicates that a junction (such as a road or rail intersection) has been assigned an official identifying number within a network.
-
D.
servesJunction
Indicates that one element functions as a connecting or branching point where multiple other elements meet or intersect.
-
E.
isJunction
Indicates that an entity functions as a junction point where multiple paths, lines, or connections meet or intersect.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
Created at: April 27, 2026, 12:25 p.m.