Triple
T24972411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altun Ha |
E624927
|
entity |
| Predicate | timeOfInitialOccupation |
P71101
|
FINISHED |
| Object | Preclassic period |
—
|
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: Preclassic period | Statement: [Altun Ha, timeOfInitialOccupation, Preclassic period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfInitialOccupation Context triple: [Altun Ha, timeOfInitialOccupation, Preclassic period]
-
A.
occupationDate
chosen
Indicates the date or time period during which an entity assumes, holds, or begins a particular role, position, or occupation.
-
B.
timePeriodOfEarlierOccupation
Indicates that one entity specifies the time span during which another entity was previously occupied or held a position before a later occupation.
-
C.
wasOccupiedDuring
Indicates that an entity was under the control, presence, or use of another entity throughout a specified time period.
-
D.
firstOccupiedBy
Indicates which entity was the initial or earliest known occupant of a given place, position, or resource.
-
E.
invasionDate
Indicates the date on which an invasion event occurred or began.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:01 a.m.