Triple
T20539688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nojpetén |
E504293
|
entity |
| Predicate | conquestMethod |
P113615
|
FINISHED |
| Object | combined land and water assault |
—
|
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: combined land and water assault | Statement: [Nojpetén, conquestMethod, combined land and water assault]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conquestMethod Context triple: [Nojpetén, conquestMethod, combined land and water assault]
-
A.
typeOfConquest
Indicates the specific manner or category of conquest by which one entity gains control over or dominance of another.
-
B.
methodOfInvasion
chosen
Indicates the specific way or technique by which an invasion is carried out.
-
C.
conquestEvent
Indicates an event in which one party gains control over another entity or territory through force or domination.
-
D.
conquestPeriod
Indicates the time span during which one entity successfully subjugates or takes control of another through conquest.
-
E.
conqueredIn
Indicates that one entity gained control over another entity or territory as a result of a specific conquest event or campaign.
- 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_69e0b4b476648190bc6019622ae54d3c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a290bd8c819091988f511fb5820b |
completed | April 20, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:37 a.m.