Triple
T20072994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nojpetén |
E499784
|
entity |
| Predicate | lastMajorIndependentMayaCapital |
P61933
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
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: true | Statement: [Nojpetén, lastMajorIndependentMayaCapital, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastMajorIndependentMayaCapital Context triple: [Nojpetén, lastMajorIndependentMayaCapital, true]
-
A.
lastIndependentMayaPolity
chosen
Indicates that the subject is recognized as the final Maya political entity to maintain independence before incorporation into an external state or colonial power.
-
B.
mayorSeatOf
Indicates that a particular mayor holds office as the chief elected official of a specified city or municipality.
-
C.
inauguratedAsCapital
Indicates that a place was officially declared and established as the capital of a political or administrative entity.
-
D.
associatedDynastyCapital
Indicates a relationship where a dynasty is linked to the city that served as its capital.
-
E.
NojpeténWas
Indicates that something is identified as, or took place in, the historical city of Nojpetén.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e664392c748190a6cc472f80b8c74b |
completed | April 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:40 p.m.