Triple
T4068182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Witney (UK Parliament constituency) |
E86378
|
entity |
| Predicate | mapsToWestminster |
P9923
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Witney (UK Parliament constituency), mapsToWestminster, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapsToWestminster Context triple: [Witney (UK Parliament constituency), mapsToWestminster, Yes]
-
A.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central London.
-
B.
directionFromLondon
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
-
C.
mapsTo
chosen
Indicates that one entity is associated with or transformed into another entity, typically defining a directional correspondence or function from a source to a target.
-
D.
mapsFrom
Indicates that one entity is derived, transformed, or constructed based on data, structure, or content originating from another entity.
-
E.
directionFromManchesterCityCentre
Indicates the compass direction in which one location lies when measured outward from Manchester city centre.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbf8f33c8190a6afca1830f35485 |
completed | March 9, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69aef9061d2481908307cafc9e9b32c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.