Triple
T29385778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seurasaari bridge |
E745248
|
entity |
| Predicate | hasSeasonalUsagePeak |
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: [Seurasaari bridge, hasSeasonalUsagePeak, summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonalUsagePeak Context triple: [Seurasaari bridge, hasSeasonalUsagePeak, 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.
seasonalDemandPeak
Indicates that demand for a product, service, or resource reaches its highest level during a specific recurring season or time period.
-
C.
hasOffPeakUsage
Indicates that an entity exhibits or is associated with usage occurring during designated off-peak times rather than standard peak periods.
-
D.
isOnPeak
Indicates that one entity is located at, or positioned on, the highest point or summit of another entity.
-
E.
hasSeasonalPattern
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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: April 28, 2026, 2:38 p.m.