Triple
T13094009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sam Ratulangi International Airport |
E310532
|
entity |
| Predicate | hasTerminalServices |
P53208
|
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: [Sam Ratulangi International Airport, hasTerminalServices, check-in counters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerminalServices Context triple: [Sam Ratulangi International Airport, hasTerminalServices, check-in counters]
-
A.
supportsTerminalConnections
Indicates that one entity is capable of handling or enabling direct connections to terminal interfaces or endpoints.
-
B.
supportsRemoteTerminal
Indicates that one entity provides or enables access to another entity via a remote terminal interface.
-
C.
hasIntegratedTerminal
Indicates that one entity includes or supports a built-in terminal interface as part of its functionality.
-
D.
hasTerminalFacility
chosen
Indicates that an entity possesses or includes a terminal facility used as an endpoint for transport, communication, or related operations.
-
E.
supportsMultipleTerminals
Indicates that an entity is capable of handling or operating with more than one terminal or endpoint simultaneously.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9813cd1b881909871a318fdd60672 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:03 p.m.