Triple
T31209933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Medb |
E795707
|
entity |
| Predicate | burialPlaceLegend |
P118842
|
FINISHED |
| Object | Miosgán Medbha |
—
|
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: Miosgán Medbha | Statement: [Queen Medb, burialPlaceLegend, Miosgán Medbha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialPlaceLegend Context triple: [Queen Medb, burialPlaceLegend, Miosgán Medbha]
-
A.
burialPlace
Indicates the location where a person or entity is buried.
-
B.
burialCoordinates
Indicates the geographic location where an entity is buried, typically expressed as spatial coordinates.
-
C.
reputedBurialPlaceOf
chosen
Indicates a location that is widely believed or traditionally thought to be the burial place of a particular person or group.
-
D.
burialSiteNear
Indicates that the burial site of one entity is located geographically close to another entity.
-
E.
burialText
Indicates that a text is inscribed on, associated with, or used in connection with a burial or funerary context.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c26b2a0819099c6abe4a0b2280c |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:09 p.m.