Triple
T23572465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Becket’s Crown |
E580151
|
entity |
| Predicate | locatedInStructurePart |
P66393
|
FINISHED |
| Object | eastern end of Canterbury 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: eastern end of Canterbury Cathedral | Statement: [Becket’s Crown, locatedInStructurePart, eastern end of Canterbury Cathedral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInStructurePart Context triple: [Becket’s Crown, locatedInStructurePart, eastern end of Canterbury Cathedral]
-
A.
locatedOnStructureType
Indicates that an entity is situated on or supported by a particular type of structure.
-
B.
locationOfStructure
Indicates that a particular structure is situated at or occupies a specific location.
-
C.
locatedInTheInteriorOf
Indicates that one entity is situated entirely within the inner part or inside area of another entity, rather than on its surface or boundary.
-
D.
foundInStructure
chosen
Indicates that an entity is located within, contained by, or structurally part of another entity or structure.
-
E.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd40c9c8190b666a2010d723bf1 |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:37 p.m.