Triple
T27140785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAM AB |
E681810
|
entity |
| Predicate | managesHoldingsFor |
P33008
|
FINISHED |
| Object | Wallenberg family |
—
|
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: Wallenberg family | Statement: [FAM AB, managesHoldingsFor, Wallenberg family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesHoldingsFor Context triple: [FAM AB, managesHoldingsFor, Wallenberg family]
-
A.
developsHoldingsFor
Indicates that one entity actively manages or expands investment or asset holdings on behalf of another entity.
-
B.
managesWealthFor
chosen
Indicates that one entity is responsible for overseeing, controlling, or administering the financial assets or wealth of another entity.
-
C.
managingFor
Indicates that one entity is responsible for directing, supervising, or overseeing activities, resources, or operations on behalf of another entity.
-
D.
eraOfMajorHoldings
Indicates the historical time period during which the primary or most significant holdings associated with an entity were established or predominant.
-
E.
typicalHoldingsType
Indicates the usual or most common category of holdings associated with an entity or account.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 9:09 a.m.