Triple
T9284509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMR Corporation |
E223154
|
entity |
| Predicate | defunctAs |
P41617
|
FINISHED |
| Object | independent holding company |
—
|
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: independent holding company | Statement: [AMR Corporation, defunctAs, independent holding company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defunctAs Context triple: [AMR Corporation, defunctAs, independent holding company]
-
A.
defunctBy
Indicates that an entity has ceased to exist, operate, or function as a result of the actions, decisions, or influence of another entity.
-
B.
defunct
chosen
Indicates that an entity has ceased to exist, operate, or function and is no longer active or in use.
-
C.
deactivated
Indicates that an entity has been turned off, disabled, or rendered inactive so it no longer performs its usual function or role.
-
D.
demiseOfStatus
Indicates the ending or loss of a previously held status, role, or condition for an entity.
-
E.
scrapped
Indicates that something planned, created, or in progress was abandoned, discarded, or cancelled and will no longer be pursued or used.
- 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_69ca842123588190b3f2e1a69037d141 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd081e72988190917f425e64631837 |
completed | April 1, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:34 p.m.