Triple
T36174350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KLIA2 |
E1046538
|
entity |
| Predicate | hasCodeSharingWith |
P204777
|
FINISHED |
| Object | KLIA (as same airport code KUL) |
E83764
|
NE 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: KLIA (as same airport code KUL) | Statement: [KLIA2, hasCodeSharingWith, KLIA (as same airport code KUL)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCodeSharingWith Context triple: [KLIA2, hasCodeSharingWith, KLIA (as same airport code KUL)]
-
A.
isSharedBy
Indicates that something is jointly possessed, used, or experienced by two or more entities.
-
B.
sharesCodebaseWith
Indicates that two software systems or components are built from, or depend on, substantially the same underlying source code.
-
C.
isShared
Indicates that something is jointly used, possessed, or made accessible by more than one entity.
-
D.
hasShareRestriction
Indicates that there is a limitation or condition placed on the transfer, sale, or use of shares associated with an entity.
-
E.
hasResponsibilitiesSharedWith
Indicates that two or more entities share joint responsibility for certain tasks, duties, or obligations.
- F. None of above. chosen
Provenance (5 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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a390d5cafc481909d61c55d1aa1d891 |
completed | June 22, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:08 p.m.