Triple
T18603372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pont (Valsavarenche) |
E454673
|
entity |
| Predicate | seasonalPeakActivity |
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: [Pont (Valsavarenche), seasonalPeakActivity, summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonalPeakActivity Context triple: [Pont (Valsavarenche), seasonalPeakActivity, summer]
-
A.
hasPeakVisitationSeason
chosen
Indicates that an entity experiences its highest or most concentrated level of visitation during a specific season or time period.
-
B.
seasonalActivitiesAtTop
Indicates that certain activities occur or are available at the top of a location (such as a hill, building, or structure) only during specific seasons.
-
C.
hasSeasonalRidershipPeak
Indicates that the ridership of an entity (such as a service or route) reaches its highest levels during specific seasons or times of the year.
-
D.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
E.
summerPeak
Indicates that something reaches its highest level, intensity, or activity during the summer season.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54752abec8190a5f4aa84abe8b240 |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.