Triple
T35676439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HP |
E1030872
|
entity |
| Predicate | operatorUltimateSuccessor |
P5677
|
FINISHED |
| Object | American Airlines |
—
|
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: American Airlines | Statement: [HP, operatorUltimateSuccessor, American Airlines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorUltimateSuccessor Context triple: [HP, operatorUltimateSuccessor, American Airlines]
-
A.
successorOperator
chosen
Indicates that one operator directly follows another in a defined sequence or ordering.
-
B.
eventualSuccessor
Indicates that one entity will become the successor of another at some later point in time, rather than immediately.
-
C.
successorAct
Indicates that one action or event directly follows and replaces another in a sequence or process.
-
D.
successorInCommand
Indicates that one entity is designated to assume command authority immediately after another entity, typically when the latter is unavailable or their term ends.
-
E.
successorUse
Indicates that one entity is used or applied as the subsequent or follow-up use of another entity in a sequence or lifecycle.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a016ebba0448190b5319243e1b2feca |
completed | May 11, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_6a016d2486b4819085efe197ee21b707 |
completed | May 11, 2026, 5:46 a.m. |
Created at: May 3, 2026, 4:05 p.m.