Triple
T5942733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 737 MAX 9 |
E132205
|
entity |
| Predicate | aircraftStatus |
P66892
|
FINISHED |
| Object | in commercial service |
—
|
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: in commercial service | Statement: [Boeing 737 MAX 9, aircraftStatus, in commercial service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftStatus Context triple: [Boeing 737 MAX 9, aircraftStatus, in commercial service]
-
A.
airportStatus
Indicates the current operational condition or state of an airport (e.g., open, closed, delayed, restricted).
-
B.
IATAStatus
Indicates the current operational or membership status of an entity with respect to the International Air Transport Association (IATA).
-
C.
cityTerminalStatus
Indicates the operational or functional status of a city’s terminal (such as an airport, bus, or train terminal) within a given context or system.
-
D.
formerAirportStatus
Indicates that an entity previously held the status of an airport but no longer functions as one.
-
E.
landerStatus
Indicates the current operational or situational state of a lander in its mission lifecycle.
- 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_69c00869d3308190af89b2453e0f7546 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0335806788190b6488ca8b73f7a63 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03edf98b881908e9dbc03d3fd6218 |
completed | March 22, 2026, 7:11 p.m. |
Created at: March 22, 2026, 4:01 p.m.