Triple
T1350718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya civilization |
E28873
|
entity |
| Predicate | conquestPeriod |
P26883
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Maya civilization, conquestPeriod, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conquestPeriod Context triple: [Maya civilization, conquestPeriod, 16th century]
-
A.
conquestYear
Indicates the year in which one entity successfully conquered or took control over another entity.
-
B.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
C.
conquestEvent
Indicates an event in which one party gains control over another entity or territory through force or domination.
-
D.
conqueredFrom
Indicates that one entity gained control of another entity by taking it from a third party that previously held it.
-
E.
warPeriod
Indicates a time span during which a state of war or armed conflict is ongoing between parties.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c26981d081909ca3b8d8cdf7cf2e |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf60545c8190901ccfb2cb7c4b41 |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:56 p.m.