Triple
T29434282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noida International Airport |
E746523
|
entity |
| Predicate | plannedOpeningPhase1 |
P51679
|
FINISHED |
| Object | 2025 |
—
|
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: 2025 | Statement: [Noida International Airport, plannedOpeningPhase1, 2025]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedOpeningPhase1 Context triple: [Noida International Airport, plannedOpeningPhase1, 2025]
-
A.
phase1OpeningDate
chosen
Indicates the date on which the first phase of a project, development, or initiative is officially opened or begins operation.
-
B.
plannedOpeningPeriod
Indicates the time span during which something is scheduled or intended to open or begin operating.
-
C.
plannedOpeningDate
Indicates the date on which something is scheduled or intended to begin operating or become available.
-
D.
hasPlannedOpening
Indicates that an entity is scheduled or intended to begin operating or become available at a specified future time or date.
-
E.
phasedOpening
Indicates that the opening or launch of something occurs in multiple planned stages or phases rather than all at once.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 28, 2026, 3:15 p.m.