Triple
T16956458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Gate (Oxford) |
E411316
|
entity |
| Predicate | directionOfApproachControlled |
P31133
|
FINISHED |
| Object | southern approach to Oxford |
—
|
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: southern approach to Oxford | Statement: [South Gate (Oxford), directionOfApproachControlled, southern approach to Oxford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionOfApproachControlled Context triple: [South Gate (Oxford), directionOfApproachControlled, southern approach to Oxford]
-
A.
approachControl
Indicates that one entity moves closer to another entity in a deliberate or controlled manner.
-
B.
approachDirection
chosen
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
C.
controlledApproachTo
Indicates a deliberate, regulated, or carefully managed way of proceeding toward or dealing with another entity.
-
D.
hasApproachControl
Indicates that one entity exercises approach control authority or responsibility over another entity, typically managing its approach phase or access.
-
E.
approachOver
Indicates that one entity moves closer to another entity from a position above or higher than 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d01c7b408190b5a2b6c62b050b76 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.