Triple
T8645940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grove, Oxfordshire |
E204976
|
entity |
| Predicate | directionFromWantage |
P40031
|
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: [Grove, Oxfordshire, directionFromWantage, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromWantage Context triple: [Grove, Oxfordshire, directionFromWantage, north]
-
A.
directionRelativeTo
Indicates the spatial orientation of one entity in relation to another, such as which way it faces or points relative to a reference entity.
-
B.
geographicDirectionImpliedByName
Indicates that the name of a place or feature suggests a specific geographic direction (e.g., north, south, east, west) relative to some reference.
-
C.
directionFromEarth
Indicates the compass or spatial direction in which an entity is located as observed from Earth.
-
D.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
E.
approximateDirection
chosen
Indicates that one entity is located in a general or rough directional relation (e.g., roughly north, south, etc.) relative to another entity, without specifying an exact bearing.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc480eb7f88190a38d2150976cd47f |
completed | March 31, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:28 p.m.