Triple
T32912087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cowles, New Mexico |
E841904
|
entity |
| Predicate | hasSeasonalActivityPeak |
P955
|
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: [Cowles, New Mexico, hasSeasonalActivityPeak, summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonalActivityPeak Context triple: [Cowles, New Mexico, hasSeasonalActivityPeak, summer]
-
A.
hasPeakVisitationSeason
Indicates that an entity experiences its highest or most concentrated level of visitation during a specific season or time period.
-
B.
hasSeasonalEvents
Indicates that an entity organizes or experiences events that occur only during specific seasons or times of the year.
-
C.
seasonalDemandPeak
Indicates that demand for a product, service, or resource reaches its highest level during a specific recurring season or time period.
-
D.
hasSeasonalPractice
Indicates that an entity engages in a practice or activity that occurs or is performed during specific seasons or recurring seasonal periods.
-
E.
hasSeasonalPattern
chosen
Indicates that the occurrence, intensity, or characteristics of something regularly vary according to a recurring seasonal cycle.
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
Created at: May 1, 2026, 1:19 a.m.