Triple
T35677690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enso |
E1030908
|
entity |
| Predicate | notableCompanySuccessor |
P198820
|
FINISHED |
| Object | Stora Enso |
E681817
|
NE 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: Stora Enso | Statement: [Enso, notableCompanySuccessor, Stora Enso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCompanySuccessor Context triple: [Enso, notableCompanySuccessor, Stora Enso]
-
A.
hasCorporateSuccessor
Indicates that one corporate entity is the legal successor to another, inheriting its rights, obligations, or continuity of business.
-
B.
notableSuccessor
Indicates that one entity is a prominent or historically significant successor to another in a sequence or lineage.
-
C.
notableSuccessorFunction
Indicates that one entity is recognized as a significant or noteworthy successor to another in a sequence, role, or function.
-
D.
hasNotableSuccessorCompany
chosen
Indicates that an entity is followed by another company recognized as a particularly important or prominent successor.
-
E.
notableSuccessorUnit
Indicates that one unit is recognized as a particularly significant or prominent successor to another unit in a sequence or lineage.
- F. None of above.
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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38728954388190b2631fe479f59f58 |
completed | June 21, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.