Triple
T34119114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petexbatún region |
E875064
|
entity |
| Predicate | peakOccupation |
P178418
|
FINISHED |
| Object | Late Classic 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: Late Classic period | Statement: [Petexbatún region, peakOccupation, Late Classic period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakOccupation Context triple: [Petexbatún region, peakOccupation, Late Classic period]
-
A.
peakUse
Indicates the time, condition, or context in which something reaches its maximum level of use or intensity.
-
B.
peakDayAttendance
Indicates the number of attendees present on the single highest-attendance day within a given period or event.
-
C.
hasNumberOfSeatsAtPeak
Indicates the maximum number of seats available or occupied at the peak usage or capacity of something.
-
D.
operatorAtPeak
Indicates that an operator is present and performing their role at the peak or highest point of a process, structure, or operational cycle.
-
E.
operationalPeak
Indicates the highest level or period of performance, capacity, or activity that a system, process, or entity reaches during its operation.
- 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7107acf0481909b01467b9ebbde01 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fb41a9c8190a121e62e510dc18a |
completed | May 3, 2026, 9:04 a.m. |
Created at: May 1, 2026, 1:53 a.m.