Triple
T35652938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wesco Financial Corporation |
E1030201
|
entity |
| Predicate | hasViceChairman |
P16596
|
FINISHED |
| Object | Charles T. Munger |
—
|
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: Charles T. Munger | Statement: [Wesco Financial Corporation, hasViceChairman, Charles T. Munger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViceChairman Context triple: [Wesco Financial Corporation, hasViceChairman, Charles T. Munger]
-
A.
hasViceChair
chosen
Indicates that an entity holds the role or position of vice chair in relation to another entity (such as an organization, committee, or group).
-
B.
hasViceChairTitle
Indicates that an entity holds the position or bears the formal title of vice chair in relation to another entity or organization.
-
C.
hasFormerViceChairperson
Indicates that an entity previously held the role of vice chairperson of another entity.
-
D.
hasChairmanIn
Indicates that an entity has a person serving as its chairman in a specified organization, location, or context.
-
E.
hasCoChair
Indicates that an entity shares the role of chair (leadership or oversight position) jointly with another entity.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 3, 2026, 4:05 p.m.