Triple
T32599940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orbital ATK |
E833336
|
entity |
| Predicate | ceasedToExistAsIndependentCompanyOn |
P62226
|
FINISHED |
| Object | 2018-06-06 |
—
|
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: 2018-06-06 | Statement: [Orbital ATK, ceasedToExistAsIndependentCompanyOn, 2018-06-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasedToExistAsIndependentCompanyOn Context triple: [Orbital ATK, ceasedToExistAsIndependentCompanyOn, 2018-06-06]
-
A.
becameIndependentCompanyOn
Indicates the date on which an entity separated from a parent or larger organization and started operating as an independent company.
-
B.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
-
C.
ceaseToExistDecisionDate
Indicates the date on which a formal decision was made that something will cease to exist or be terminated.
-
D.
associatedCompanyDefunctYear
Indicates the year in which the associated company ceased to exist or became defunct.
-
E.
disbandedAt
chosen
Indicates the time or date at which an organized group, body, or entity formally ceased to exist or operate.
- 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c69918108190afce924b83211903 |
completed | May 3, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:05 a.m.