Triple
T26650645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandpiper Air |
E669040
|
entity |
| Predicate | hasRivalAirline |
P165862
|
FINISHED |
| Object | AeroMass |
—
|
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: AeroMass | Statement: [Sandpiper Air, hasRivalAirline, AeroMass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRivalAirline Context triple: [Sandpiper Air, hasRivalAirline, AeroMass]
-
A.
hasSisterAirline
Indicates that one airline is related to another as its sister airline, typically sharing common ownership, management, or branding.
-
B.
hasAirlines
Indicates that one entity (such as an airport, city, or country) is served by or associated with one or more airline operators.
-
C.
ownsAirline
Indicates that one entity has legal ownership or controlling interest in an airline company.
-
D.
flightPartner
Indicates that two entities are associated as partners in operating, marketing, or coordinating a flight or set of flights.
-
E.
successorAirline
Indicates that one airline has taken over, replaced, or continued the operations of another airline as its successor.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a9cb0bc8190bf8a9b319900bad5 |
completed | May 2, 2026, 8:12 p.m. |
Created at: April 27, 2026, 2:32 a.m.