Triple
T16897001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PAA |
E424330
|
entity |
| Predicate | airlineNotableFor |
P22
|
FINISHED |
| Object | developing global route networks |
—
|
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: developing global route networks | Statement: [PAA, airlineNotableFor, developing global route networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineNotableFor Context triple: [PAA, airlineNotableFor, developing global route networks]
-
A.
referredAircraftNotableFeature
Indicates that a referenced aircraft is associated with a notable or distinguishing feature.
-
B.
notablePilot
Indicates that an entity is a distinguished or noteworthy pilot associated with another entity (such as a vehicle, event, or organization).
-
C.
notableHotel
Indicates that a hotel is notable or significant in some recognized way, such as historical, cultural, or commercial importance.
-
D.
notableFor
chosen
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
E.
usedByAirlineAlsoKnownAs
Indicates that an item (such as a code, name, or identifier) is used by an airline that is also known by an alternative name.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8d880208190ad2b2c8616b54ea3 |
completed | April 18, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.