Triple
T26297621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yik'in Chan K'awiil |
E661460
|
entity |
| Predicate | notableConquest |
P61707
|
FINISHED |
| Object | Calakmul |
—
|
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: Calakmul | Statement: [Yik'in Chan K'awiil, notableConquest, Calakmul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableConquest Context triple: [Yik'in Chan K'awiil, notableConquest, Calakmul]
-
A.
conquestEvent
Indicates an event in which one party gains control over another entity or territory through force or domination.
-
B.
notableCrusade
Indicates that an entity is significantly associated with, or distinguished for its involvement in, a particular Crusade.
-
C.
associatedWithMilitaryConquests
chosen
Indicates a relationship where an entity is connected to, involved in, or characterized by military conquests or campaigns.
-
D.
conquestCampaign
Indicates a military or strategic campaign undertaken with the goal of conquering and taking control of a target entity or territory.
-
E.
realmConqueredBy
Indicates that a particular realm or territory has been taken over and brought under the control of a specified conqueror.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: April 26, 2026, 10:13 p.m.