Triple
T7533895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiroshima Airport |
E178097
|
entity |
| Predicate | runwaySupports |
P46124
|
FINISHED |
| Object | wide-body aircraft operations |
—
|
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: wide-body aircraft operations | Statement: [Hiroshima Airport, runwaySupports, wide-body aircraft operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwaySupports Context triple: [Hiroshima Airport, runwaySupports, wide-body aircraft operations]
-
A.
runwaySupportsAircraftType
chosen
Indicates that a particular runway is suitable and certified for use by a specified type of aircraft.
-
B.
runwayRequirement
Indicates the minimum runway characteristics (such as length or surface conditions) needed for an aircraft or operation to take off or land safely.
-
C.
hasRunwayType
Indicates that an airport or airfield has a runway of a specified type or surface classification.
-
D.
isRunwayOf
Indicates that a physical runway is a component or facility belonging to, used by, or officially associated with a particular airport or airfield.
-
E.
hasRunwayPresence
Indicates that an entity maintains a physical runway or landing strip suitable for aircraft operations.
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8493964819086aeddfa4872a70b |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.