Triple
T28052574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REDWOOD |
E708866
|
entity |
| Predicate | successorAirlineCallsSign |
P192360
|
FINISHED |
| Object | Alaska |
—
|
NE NERFINISHED |
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: Alaska | Statement: [REDWOOD, successorAirlineCallsSign, Alaska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAirlineCallsSign Context triple: [REDWOOD, successorAirlineCallsSign, Alaska]
-
A.
successorAirline
Indicates that one airline has taken over, replaced, or continued the operations of another airline as its successor.
-
B.
airlineFormerName
Indicates that an airline previously operated under a different name, specifying its former official designation.
-
C.
airlineICAOcallsign
Indicates the official ICAO radio callsign phrase used to identify a specific airline in air traffic communications.
-
D.
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.
-
E.
operatingAirlineCallsign
Indicates the radio callsign used by the airline that is actually operating the flight.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69fd098357348190a835c0b6d99857d2 |
completed | May 7, 2026, 9:52 p.m. |
Created at: April 27, 2026, 8:34 p.m.