Triple
T20562124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacKenzie Falls |
E504867
|
entity |
| Predicate | peakVisitationPeriod |
P127382
|
FINISHED |
| Object | summer |
—
|
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: summer | Statement: [MacKenzie Falls, peakVisitationPeriod, summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakVisitationPeriod Context triple: [MacKenzie Falls, peakVisitationPeriod, summer]
-
A.
peakServicePeriod
Indicates the time interval during which a service experiences its highest or most intensive level of use or operation.
-
B.
peakExportPeriod
Indicates the time period during which exports of a given item or from a given source reach their highest level.
-
C.
hasPeakVisitationSeason
chosen
Indicates that an entity experiences its highest or most concentrated level of visitation during a specific season or time period.
-
D.
peakDayAttendance
Indicates the number of attendees present on the single highest-attendance day within a given period or event.
-
E.
peakDays
Indicates the days on which something reaches its highest or most intense level of activity, usage, or occurrence.
- 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a79f906c819081163de9649ccb17 |
completed | April 20, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.