Triple
T3822806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hel Peninsula railway line |
E88614
|
entity |
| Predicate | seasonalTraffic |
P45121
|
FINISHED |
| Object | high summer tourist traffic |
—
|
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: high summer tourist traffic | Statement: [Hel Peninsula railway line, seasonalTraffic, high summer tourist traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonalTraffic Context triple: [Hel Peninsula railway line, seasonalTraffic, high summer tourist traffic]
-
A.
servesSeasonalTraffic
chosen
Indicates that an entity provides service only during specific seasons or periods of the year, rather than year-round.
-
B.
annualTraffic
Indicates the typical amount or volume of traffic associated with something over the course of a year.
-
C.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
D.
roadTraffic
Indicates the presence, flow, or conditions of vehicles and movement along roads or streets.
-
E.
passengerTraffic
Indicates the flow or volume of passengers moving through or using a particular transport service, route, or facility.
- 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_69aed9538cf881909d9ce8ca4ac7c18c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee74a2bc081909b237df8b1e27653 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.