Triple
T281960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King's Day |
E5371
|
entity |
| Predicate | publicTransportStatus |
P9581
|
FINISHED |
| Object | often operates on special schedules |
—
|
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: often operates on special schedules | Statement: [King's Day, publicTransportStatus, often operates on special schedules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicTransportStatus Context triple: [King's Day, publicTransportStatus, often operates on special schedules]
-
A.
publicTransitStop
Indicates that a location serves as a designated stop or station where public transit vehicles (such as buses, trains, or trams) pick up and drop off passengers.
-
B.
hasBusStation
Indicates that a place or area contains or is served by a bus station.
-
C.
publicTransit
Indicates that one entity provides or is connected via shared, scheduled transportation services (such as buses, trains, or subways) that are available for use by the general public.
-
D.
paratransitSystemName
Indicates the name assigned to a specific paratransit transportation system or service.
-
E.
busSystemName
Indicates that a bus system is identified or referred to by a specific name.
- F. None of above. chosen
Provenance (4 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25e0a23c0819083abee28b2dea49c |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b77e028819087e606fc321219f7 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25e06dd7c8190a8cbb76cee3c6e4b |
completed | Feb. 28, 2026, 3:16 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.