Triple
T15528748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molde Airport, Årø |
E370152
|
entity |
| Predicate | hasTerminalService |
P119039
|
FINISHED |
| Object | check-in counters |
—
|
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: check-in counters | Statement: [Molde Airport, Årø, hasTerminalService, check-in counters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerminalService Context triple: [Molde Airport, Årø, hasTerminalService, check-in counters]
-
A.
hasTerminalFacility
Indicates that an entity possesses or includes a terminal facility used as an endpoint for transport, communication, or related operations.
-
B.
hasIntegratedTerminal
Indicates that one entity includes or supports a built-in terminal interface as part of its functionality.
-
C.
servesTerminal
Indicates that one entity functions as a terminal or endpoint facility that is served or operated by another entity.
-
D.
supportsTerminalConnections
Indicates that one entity is capable of handling or enabling direct connections to terminal interfaces or endpoints.
-
E.
hasTerminalFunction
Indicates that something possesses a function or role specifically associated with an endpoint, boundary, or final stage within a system or process.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0414620588190958ffde651ccab5f |
completed | April 16, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_69ded28ab0588190a47a9090d1238707 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57165288190979b7acb71ad5145 |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 4:05 a.m.