Triple
T8433949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charred Cross of Coventry |
E199179
|
entity |
| Predicate | positionedAt |
P3250
|
FINISHED |
| Object | altar of the ruined Coventry Cathedral |
—
|
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: altar of the ruined Coventry Cathedral | Statement: [Charred Cross of Coventry, positionedAt, altar of the ruined Coventry Cathedral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionedAt Context triple: [Charred Cross of Coventry, positionedAt, altar of the ruined Coventry Cathedral]
-
A.
positionEstablishedIn
Indicates the point in time or event when a particular position, role, or office was formally created or instituted.
-
B.
positionOn
chosen
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
-
D.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
E.
positionEstablishedFor
Indicates that a specific role or job position has been formally created or set up for a particular entity or purpose.
- 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_69ca8314cd6c8190a6b8c2a1096e18f3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0ec200c8190b0299e2b0b4bdcc2 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:07 p.m.