Triple
T27563718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya ruins at Palenque |
E695839
|
entity |
| Predicate | hasRulerBurial |
P62966
|
FINISHED |
| Object | Kʼinich Janaabʼ Pakal I |
—
|
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: Kʼinich Janaabʼ Pakal I | Statement: [Maya ruins at Palenque, hasRulerBurial, Kʼinich Janaabʼ Pakal I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRulerBurial Context triple: [Maya ruins at Palenque, hasRulerBurial, Kʼinich Janaabʼ Pakal I]
-
A.
hasBurialsOf
chosen
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
-
B.
hasBurialVault
Indicates that an entity possesses or is associated with a specific burial vault used for interment or storage of remains.
-
C.
hasBurialCustoms
Indicates that a group, culture, or society practices specific rituals or customs related to the treatment and burial of the dead.
-
D.
hasBuriedRemains
Indicates that one entity contains or is the location of the buried remains of another entity.
-
E.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 1:40 p.m.