Triple
T36563647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sundon Park |
E901911
|
entity |
| Predicate | geographicDirectionWithinLuton |
P162116
|
FINISHED |
| Object | north |
—
|
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: north | Statement: [Sundon Park, geographicDirectionWithinLuton, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicDirectionWithinLuton Context triple: [Sundon Park, geographicDirectionWithinLuton, north]
-
A.
directionFromLondon
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
-
B.
geographicalDirectionWithinCounty
chosen
Indicates that one location lies in a specified cardinal or intercardinal direction relative to another location within the same county.
-
C.
isInDirectionTowardsCentralLondon
Indicates that something is oriented or moving in the direction leading toward central London.
-
D.
geographicDirectionWithinFlintshire
Indicates the relative geographic direction of one place or feature with respect to another, specifically within the boundaries of Flintshire.
-
E.
lineDirectionFromCentralLondon
Indicates the directional bearing or route of a line as measured outward from a central reference point in London.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:11 p.m.