Triple
T37624292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A13 at Sadlers Farm |
E936159
|
entity |
| Predicate | connectsDirectionFromA13 |
P82340
|
FINISHED |
| Object | London |
—
|
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: London | Statement: [A13 at Sadlers Farm, connectsDirectionFromA13, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsDirectionFromA13 Context triple: [A13 at Sadlers Farm, connectsDirectionFromA13, London]
-
A.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
B.
connectionDirection
chosen
Indicates the directional flow or orientation of a connection from one entity to another.
-
C.
connectsCentralAreaTo
Indicates a relationship where one element serves as a link or pathway between a central area and another location or component.
-
D.
connectsCountryDirection
Indicates that one country is geographically connected to another in a specified cardinal or relative direction (e.g., north, south, east, west).
-
E.
connectsTerminus
Indicates that one entity serves as a terminus that is directly linked or joined to another entity.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fff4530f908190afe9387f732c2b7e |
completed | May 10, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fff3c01a64819091196875b0c88607 |
completed | May 10, 2026, 2:56 a.m. |
Created at: May 3, 2026, 4:18 p.m.