Triple
T8797022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Changi Airports International |
E209313
|
entity |
| Predicate | typicalCounterparty |
P28668
|
FINISHED |
| Object | airport authorities |
—
|
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: airport authorities | Statement: [Changi Airports International, typicalCounterparty, airport authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCounterparty Context triple: [Changi Airports International, typicalCounterparty, airport authorities]
-
A.
counterpartService
Indicates that one service functions as the corresponding or matching service to another within a defined relationship or context.
-
B.
tradingPartner
chosen
Indicates a relationship where two entities engage in the exchange of goods, services, or financial instruments with one another.
-
C.
hasCounterpart
Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
-
D.
monetaryAgreementPartner
Indicates that two entities are bound by a financial or payment-related agreement or partnership.
-
E.
participatingParty
Indicates that an entity is involved as a participant in a particular event, activity, or transaction.
- 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_69ca836240888190a62b262e56a69d2f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fa370d08190885ef65e3a3e56d3 |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:44 p.m.