Triple
T16835151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | klia2 |
E409254
|
entity |
| Predicate | terminalCode |
P38513
|
FINISHED |
| Object | Terminal 2 |
—
|
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: Terminal 2 | Statement: [klia2, terminalCode, Terminal 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalCode Context triple: [klia2, terminalCode, Terminal 2]
-
A.
terminalFunction
Indicates that an entity serves as an endpoint or final functional unit within a larger structure, process, or system.
-
B.
terminalName
chosen
Indicates the name or label assigned to a specific terminal or endpoint within a system or network.
-
C.
terminal
Indicates that one entity is the final or end point in a process, sequence, or structure, beyond which no further continuation occurs.
-
D.
terminalDesign
Indicates a relationship where an entity is responsible for or characterized by the design or configuration of a terminal or terminal-like interface.
-
E.
terminalForm
Indicates that one entity represents the final or end-state form of another entity within a process, sequence, or transformation.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b31aa44c8190b4f402f1898e6998 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.