Triple
T4054377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford city walls |
E84658
|
entity |
| Predicate | enclosed |
P14700
|
FINISHED |
| Object | historic centre 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: historic centre of Oxford | Statement: [Oxford city walls, enclosed, historic centre of Oxford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enclosed Context triple: [Oxford city walls, enclosed, historic centre of Oxford]
-
A.
containedWith
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
-
B.
enclosesCountry
Indicates that one geopolitical entity completely surrounds or contains the territory of another country within its boundaries.
-
C.
closingContains
Indicates that one closing element, event, or period fully includes another within its temporal or structural bounds.
-
D.
closure
Indicates that an entity is closed or not accessible/available for use, entry, or interaction.
-
E.
closedIn
chosen
Indicates that one entity is enclosed, contained, or surrounded within the boundaries or limits defined by another entity.
- 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbaa84b88190856e179266769e6d |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.