Triple
T31906501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mauritz Widforss |
E814566
|
entity |
| Predicate | hasBusinessSuccessor |
P53829
|
FINISHED |
| Object | H&M |
—
|
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: H&M | Statement: [Mauritz Widforss, hasBusinessSuccessor, H&M]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusinessSuccessor Context triple: [Mauritz Widforss, hasBusinessSuccessor, H&M]
-
A.
hasCorporateSuccessor
Indicates that one corporate entity is the legal successor to another, inheriting its rights, obligations, or continuity of business.
-
B.
hasLegalSuccessor
Indicates that one entity is the legally recognized successor or inheritor of another entity’s rights, obligations, or status.
-
C.
hasBusinessSuccession
chosen
Indicates that one business entity continues, replaces, or inherits the operations, rights, or obligations of another business over time.
-
D.
hasSuccession
Indicates that one entity follows or replaces another in a sequence, order, or position, forming a succession relationship between them.
-
E.
hasOfficialSuccessorName
Indicates that an entity has an officially designated successor identified by a specific name.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 1, 2026, midnight