Triple
T25629571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tikal dynasty |
E642533
|
entity |
| Predicate | hasBurialPlaceForRulers |
P159783
|
FINISHED |
| Object | North Acropolis of Tikal |
—
|
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: North Acropolis of Tikal | Statement: [Tikal dynasty, hasBurialPlaceForRulers, North Acropolis of Tikal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBurialPlaceForRulers Context triple: [Tikal dynasty, hasBurialPlaceForRulers, North Acropolis of Tikal]
-
A.
founderOfDynastyBuried
Indicates that the founder of a dynasty is buried at a specified location.
-
B.
reputedBurialPlaceOf
Indicates a location that is widely believed or traditionally thought to be the burial place of a particular person or group.
-
C.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
D.
burialPlace
Indicates the location where a person or entity is buried.
-
E.
restingPlaceOf
Indicates the location where an entity is laid to rest, stored, or kept, typically as its final or usual resting location.
- F. None of above. chosen
Provenance (4 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa260734819080d7d32c6912d267 |
completed | May 2, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 21, 2026, 5:17 p.m.