Triple
T33233646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Blasii Cathedral |
E850767
|
entity |
| Predicate | formerBurialSiteOf |
P60564
|
FINISHED |
| Object | Henry the Lion |
—
|
NE NERFINISHED |
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: Henry the Lion | Statement: [St. Blasii Cathedral, formerBurialSiteOf, Henry the Lion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerBurialSiteOf Context triple: [St. Blasii Cathedral, formerBurialSiteOf, Henry the Lion]
-
A.
burialPlace
Indicates the location where a person or entity is buried.
-
B.
reputedBurialPlaceOf
Indicates a location that is widely believed or traditionally thought to be the burial place of a particular person or group.
-
C.
originalBurialSiteOfRemainsLaterMovedTo
chosen
Indicates that a location was the initial burial site of human remains that were subsequently relocated to another place.
-
D.
formerGraveOf
Indicates that a location once served as the grave of an entity, but no longer does (e.g., the remains have been moved or the grave has been removed).
-
E.
buriedNear
Indicates that one entity is interred or buried in close physical proximity to 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffb1f0b03c81909ddb81f07ce74e88 |
completed | May 9, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ffb1662b2481908582e0612744f4c5 |
completed | May 9, 2026, 10:12 p.m. |
Created at: May 1, 2026, 1:31 a.m.