Triple
T3463814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hovenweep National Monument |
E73087
|
entity |
| Predicate | peakOccupationPeriod |
P35920
|
FINISHED |
| Object | approximately AD 1200–1300 |
—
|
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: approximately AD 1200–1300 | Statement: [Hovenweep National Monument, peakOccupationPeriod, approximately AD 1200–1300]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakOccupationPeriod Context triple: [Hovenweep National Monument, peakOccupationPeriod, approximately AD 1200–1300]
-
A.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
B.
peakDayAttendance
Indicates the number of attendees present on the single highest-attendance day within a given period or event.
-
C.
peakUse
chosen
Indicates the time, condition, or context in which something reaches its maximum level of use or intensity.
-
D.
usagePeak
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
-
E.
shortPeriodOccupationBy
Indicates that an entity temporarily occupies or uses another entity for a relatively brief period of time.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb0b73f481908c9f8d2b9b9bbbaf |
completed | March 8, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.