Triple
T16956403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Gate |
E411314
|
entity |
| Predicate | positionRelativeToCity |
P102712
|
FINISHED |
| Object | northern side of 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: northern side of Oxford | Statement: [North Gate, positionRelativeToCity, northern side of Oxford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToCity Context triple: [North Gate, positionRelativeToCity, northern side of Oxford]
-
A.
hasRelativePositionInCity
chosen
Indicates that one entity occupies a specific spatial or positional relationship within the boundaries or layout of a particular city.
-
B.
locationRelativeToLargestCity
Indicates how a place is spatially positioned or oriented in relation to the largest city in a given area or region.
-
C.
positionOnCityCircle
Indicates that one entity is located along the circular boundary or ring-shaped layout defined by a city.
-
D.
cityLocation
Indicates that a city is geographically situated within or associated with a specific larger area or place.
-
E.
relativeHeightAboveCity
Indicates the vertical height of an entity measured above the reference elevation level of a specified city.
- 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.