Triple
T34439646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal 4 (Changi Airport) |
E884061
|
entity |
| Predicate | hasCheckInConcept |
P18843
|
FINISHED |
| Object | self-service |
—
|
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: self-service | Statement: [Terminal 4 (Changi Airport), hasCheckInConcept, self-service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCheckInConcept Context triple: [Terminal 4 (Changi Airport), hasCheckInConcept, self-service]
-
A.
hasCheckInFor
Indicates that an entity has an associated check-in record or event corresponding to another specified entity or context.
-
B.
hasCheckInProcedure
Indicates that there is a defined process or set of steps required for an entity to check in or be checked in.
-
C.
hasCheckInCategory
chosen
Indicates that an entity is associated with a specific category or type of check-in event.
-
D.
hasCheckInSystem
Indicates that an entity uses or is equipped with a system for registering or recording check-ins.
-
E.
hasCheckInFunction
Indicates that an entity provides or supports a check-in capability, such as recording or registering arrivals or presence.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 1, 2026, 2 a.m.