Triple
T16940037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gran Quivira |
E410926
|
entity |
| Predicate | timeOfPeakOccupation |
P124192
|
FINISHED |
| Object | circa 1200–1600 CE |
—
|
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: circa 1200–1600 CE | Statement: [Gran Quivira, timeOfPeakOccupation, circa 1200–1600 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfPeakOccupation Context triple: [Gran Quivira, timeOfPeakOccupation, circa 1200–1600 CE]
-
A.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
B.
operationalPeak
Indicates the highest level or period of performance, capacity, or activity that a system, process, or entity reaches during its operation.
-
C.
peakDayAttendance
Indicates the number of attendees present on the single highest-attendance day within a given period or event.
-
D.
numberOfSeatsPeakApprox
Indicates an approximate count of seats available or occupied during peak usage or demand periods.
-
E.
timeOfPeakSize
chosen
Indicates the specific time at which something reaches its maximum size or extent.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2c44288190a105761ae646989e |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.