Triple
T38691902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HDA |
E949288
|
entity |
| Predicate | previousAirlineName |
P124493
|
FINISHED |
| Object | Dragonair |
—
|
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: Dragonair | Statement: [HDA, previousAirlineName, Dragonair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousAirlineName Context triple: [HDA, previousAirlineName, Dragonair]
-
A.
airlineFormerName
chosen
Indicates that an airline previously operated under a different name, specifying its former official designation.
-
B.
userAirlineIATAName
Indicates that a user is associated with an airline identified by its IATA code and corresponding airline name.
-
C.
airlineUsed
Indicates that a particular airline is employed or chosen for transporting someone or something in a given trip or flight.
-
D.
successorAirline
Indicates that one airline has taken over, replaced, or continued the operations of another airline as its successor.
-
E.
formerIATAcode
Indicates that an entity previously held a specific IATA code, which is no longer its current assigned code.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0019b0e9fc81909494320f05e81742 |
completed | May 10, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a00193379e0819096d1985686ce10e3 |
completed | May 10, 2026, 5:35 a.m. |
Created at: May 3, 2026, 4:33 p.m.