Triple
T26931869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nojpetén |
E678246
|
entity |
| Predicate | remainedUnconqueredUntil |
P61932
|
FINISHED |
| Object | 1697 |
—
|
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: 1697 | Statement: [Nojpetén, remainedUnconqueredUntil, 1697]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remainedUnconqueredUntil Context triple: [Nojpetén, remainedUnconqueredUntil, 1697]
-
A.
notConqueredBy
Indicates that one entity has not been taken over, subdued, or brought under the control of another entity.
-
B.
conqueredIn
Indicates that one entity gained control over another entity or territory as a result of a specific conquest event or campaign.
-
C.
hasConquered
Indicates that one entity has taken control over another entity or its territory through force or domination.
-
D.
resistedUntil
chosen
Indicates that an entity continued to oppose or withstand another entity or force up to a specific point in time or event.
-
E.
afterConquestBy
Indicates that one entity exists in a state, condition, or situation that occurs subsequent to and as a result of being conquered by another entity.
- 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6204af96081908aa5d43ba7f989e5 |
completed | May 2, 2026, 4:03 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:13 a.m.