Triple
T29175388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voss Airport, Bømoen |
E739593
|
entity |
| Predicate | hasNoScheduledService |
P195123
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Voss Airport, Bømoen, hasNoScheduledService, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoScheduledService Context triple: [Voss Airport, Bømoen, hasNoScheduledService, true]
-
A.
isScheduled
Indicates that an event, task, or action has been planned and assigned a specific time or time range to occur.
-
B.
hasNoScheduledFlights
chosen
Indicates that there are currently zero flights planned or scheduled for the given entity (such as a route, airport, or airline) within the relevant time frame.
-
C.
hasTimetabledServices
Indicates that scheduled or timetabled services are provided or operate in relation to the referenced entity.
-
D.
hasServiceTime
Indicates that an entity is associated with a specific duration or schedule during which a service is provided.
-
E.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
- 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_69f07cb6394c8190ab7842c48e699e2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69ff84202eb081908ae21a54a4414d68 |
completed | May 9, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69ff833065e4819098579129d4ee17d3 |
completed | May 9, 2026, 6:55 p.m. |
Created at: April 28, 2026, 11:54 a.m.