Triple
T34393578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paya Lebar Airport |
E882770
|
entity |
| Predicate | primaryRoleBefore1981 |
P205419
|
FINISHED |
| Object | international passenger airport |
—
|
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: international passenger airport | Statement: [Paya Lebar Airport, primaryRoleBefore1981, international passenger airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoleBefore1981 Context triple: [Paya Lebar Airport, primaryRoleBefore1981, international passenger airport]
-
A.
roleAfter1971
Indicates that an entity held a particular role or position at some point after the year 1971.
-
B.
previousPrimaryAffiliationIn1980
Indicates that one entity was the main or primary affiliation of another entity specifically during the year 1980, and is no longer the current primary affiliation.
-
C.
post1978Role
Indicates a role or position that an entity held starting after the year 1978.
-
D.
primaryRoleFor
Indicates that one entity serves as the main or most important role or function for another entity.
-
E.
roleIn1950
Indicates that an entity held a particular role, position, or function in the year 1950.
- F. None of above. chosen
Provenance (4 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:59 a.m.