Triple
T4962885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satna |
E111450
|
entity |
| Predicate | hasAirportProposalStatus |
P60258
|
FINISHED |
| Object | proposed regional 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: proposed regional airport | Statement: [Satna, hasAirportProposalStatus, proposed regional airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAirportProposalStatus Context triple: [Satna, hasAirportProposalStatus, proposed regional airport]
-
A.
airportStatus
Indicates the current operational condition or state of an airport (e.g., open, closed, delayed, restricted).
-
B.
hasAirportProject
chosen
Indicates that there is a planned, ongoing, or completed airport-related development project associated with the subject entity.
-
C.
landerStatus
Indicates the current operational or situational state of a lander in its mission lifecycle.
-
D.
formerAirportStatus
Indicates that an entity previously held the status of an airport but no longer functions as one.
-
E.
hasAirportWithinJurisdiction
Indicates that a governing authority or administrative region has legal or administrative control over an airport located within its boundaries.
- 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_69bd4419393c819086319a6fe4bf8542 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd72e49b048190bac55d9e7a6f7963 |
completed | March 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69bd71447fe88190bb62c5e8753da7a7 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:32 p.m.