Triple
T29434293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noida International Airport |
E746523
|
entity |
| Predicate | areaOfAirportSite |
P59765
|
FINISHED |
| Object | over 1300 hectares (initial phases) |
—
|
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: over 1300 hectares (initial phases) | Statement: [Noida International Airport, areaOfAirportSite, over 1300 hectares (initial phases)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areaOfAirportSite Context triple: [Noida International Airport, areaOfAirportSite, over 1300 hectares (initial phases)]
-
A.
areaHectares
chosen
Indicates the size or extent of something measured in hectares.
-
B.
acquiredLandArea
Indicates the total area of land that has been obtained or taken possession of through an acquisition.
-
C.
fareArea
Indicates the geographic or zonal region within which a particular fare or pricing rule applies.
-
D.
areaApprox
Indicates that one entity’s area is approximately equal to the area of another entity.
-
E.
airfieldBuilt
Indicates that an airfield has been constructed or established, typically specifying who built it, where, and/or when.
- 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_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 3:15 p.m.