Triple
T34035746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Río Bec region |
E872790
|
entity |
| Predicate | hasPeakOccupation |
P195414
|
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: [Río Bec region, hasPeakOccupation, Late Classic period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeakOccupation Context triple: [Río Bec region, hasPeakOccupation, Late Classic period]
-
A.
hasPeak
Indicates that something possesses or contains a highest point, summit, or maximum value.
-
B.
hasPeakCount
Indicates the number of distinct peaks associated with an entity.
-
C.
hasPeakLoad
Indicates that an entity is associated with a maximum level of load or demand it experiences or can handle during a specific period.
-
D.
hasPeakOver
Indicates that one entity’s peak (such as a maximum value, height, or intensity) exceeds that of another entity.
-
E.
hasPeakAssociated
Indicates that one entity is linked or related to a specific peak (such as a summit or maximum point) associated with it.
- 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
| PDg | Predicate description generation | batch_69fdd07724f88190a33ec602642d2ea3 |
completed | May 8, 2026, noon |
Created at: May 1, 2026, 1:51 a.m.