Triple
T34393568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paya Lebar Airport |
E882770
|
entity |
| Predicate | ceasedCivilOperations |
P48787
|
FINISHED |
| Object | 1981 |
—
|
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: 1981 | Statement: [Paya Lebar Airport, ceasedCivilOperations, 1981]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasedCivilOperations Context triple: [Paya Lebar Airport, ceasedCivilOperations, 1981]
-
A.
ceasedArmedCampaign
Indicates that an entity has stopped or formally ended its use of armed force or military-style violence as a campaign or strategy.
-
B.
ceasedOperationsAs
chosen
Indicates that an entity stopped functioning or operating in a particular role, capacity, or status.
-
C.
ceasedOperationsDuring
Indicates that an entity stopped functioning or carrying out its activities at some point within the specified time period.
-
D.
isCivilMilitary
Indicates that an entity or relationship involves both civilian and military components or functions.
-
E.
civilOrMilitary
Indicates that something is classified as either civil (non-military) or military in nature or function.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.