Triple
T1902191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluewater |
E37713
|
entity |
| Predicate | positionRelativeToLondon |
P15847
|
FINISHED |
| Object | south-east of Central London |
—
|
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: south-east of Central London | Statement: [Bluewater, positionRelativeToLondon, south-east of Central London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToLondon Context triple: [Bluewater, positionRelativeToLondon, south-east of Central London]
-
A.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central London.
-
B.
directionFromLondon
chosen
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
-
C.
distanceToLondon
Indicates the measured distance between a given entity’s location and the city of London.
-
D.
positionRelativeToCoast
Indicates the spatial relationship of something to a coastline, such as its distance or orientation relative to the coast.
-
E.
relativePositionToInternationalDateLine
Indicates the spatial relationship of an entity’s location with respect to the International Date Line (e.g., whether and how it lies to the east, west, or across it).
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafe9f8b0819086d8f6288511c66d |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.