Triple
T3753893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aswan International Airport |
E81997
|
entity |
| Predicate | isRegionalAirport |
P51130
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Aswan International Airport, isRegionalAirport, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegionalAirport Context triple: [Aswan International Airport, isRegionalAirport, true]
-
A.
hasRegionalAirport
Indicates that a place or region possesses or is served by a regional airport.
-
B.
isPublicAirport
Indicates that an airport is open for use by the general public rather than restricted to private or military operations.
-
C.
isCivilAirport
Indicates that an airport is designated and used primarily for civilian (non-military) aviation operations.
-
D.
hasInternationalAirport
Indicates that a place possesses an airport that handles international flights and services cross-border air traffic.
-
E.
otherRegionalAirports
Indicates that the entities are airports located in different regions from each other but considered as alternative or comparable regional airports.
- 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_69ad8b1db40081908b61ffa6b78afd4d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb9340e0819083215989718b4598 |
completed | March 8, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc1560c248190b07438d766880990 |
completed | March 8, 2026, 6:35 p.m. |
Created at: March 8, 2026, 3:35 p.m.