Triple
T37280458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcia Roy |
E925370
|
entity |
| Predicate | roleRelativeToCompany |
P43130
|
FINISHED |
| Object | spouse of CEO Logan Roy |
—
|
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: spouse of CEO Logan Roy | Statement: [Marcia Roy, roleRelativeToCompany, spouse of CEO Logan Roy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleRelativeToCompany Context triple: [Marcia Roy, roleRelativeToCompany, spouse of CEO Logan Roy]
-
A.
roleInCompanyLifecycle
Indicates the specific function or responsibility an entity has at a particular stage of a company's lifecycle.
-
B.
underlyingCompanyRole
chosen
Indicates the specific function, position, or responsibility an entity holds within or in relation to a company.
-
C.
employerRelationship
Indicates a relationship in which one entity acts as the employer of another, having authority to hire, direct, and compensate the other party for work performed.
-
D.
socialRoleInWork
Indicates the role or position an entity holds within a work-related or professional social context.
-
E.
roleSimilarTo
Indicates that two entities have roles or functions that are alike or closely comparable in nature or responsibility.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.