Triple
T33042755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enborne |
E845512
|
entity |
| Predicate | directionFromNewbury |
P194196
|
FINISHED |
| Object | southwest |
—
|
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: southwest | Statement: [Enborne, directionFromNewbury, southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromNewbury Context triple: [Enborne, directionFromNewbury, southwest]
-
A.
directionFrom_Shrewsbury
Indicates the spatial direction in which one entity lies when measured from the location of Shrewsbury.
-
B.
directionFromBoston
Indicates the compass direction or bearing of one location as measured outward from Boston.
-
C.
directionFromStamford
Indicates the spatial direction or bearing of an entity as measured outward from Stamford.
-
D.
directionFromNewYork
Indicates the cardinal or relative compass direction of an entity or location as measured from New York.
-
E.
directionFromCanterbury
Indicates the spatial direction in which one entity lies relative to Canterbury.
- F. None of above. chosen
Provenance (4 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
| PDg | Predicate description generation | batch_69fd67182c348190aa84a02e08dbf4e1 |
completed | May 8, 2026, 4:31 a.m. |
Created at: May 1, 2026, 1:24 a.m.