Triple
T18506664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altaba Inc. |
E452213
|
entity |
| Predicate | purposeOfLiquidation |
P131929
|
FINISHED |
| Object | return capital to shareholders |
—
|
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: return capital to shareholders | Statement: [Altaba Inc., purposeOfLiquidation, return capital to shareholders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfLiquidation Context triple: [Altaba Inc., purposeOfLiquidation, return capital to shareholders]
-
A.
liquidationBegan
Indicates that the process of winding up and dissolving an entity, typically by selling its assets to pay creditors, has started.
-
B.
liquidationDate
Indicates the date on which an entity is formally wound up, dissolved, or its assets are converted to cash in a liquidation process.
-
C.
reasonForBankruptcyFiling
Indicates the cause, circumstance, or justification that led an entity to file for bankruptcy.
-
D.
purposeOfDestruction
Indicates that something is destroyed with the specific aim or intention of achieving a particular goal or outcome.
-
E.
aimOfAnnulment
Indicates that an action or legal measure has the purpose or objective of nullifying, canceling, or invalidating something.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5334266708190b59aca3a2218c095 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:36 a.m.