Triple
T335369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lynne Benioff |
E6712
|
entity |
| Predicate | knownForWorkingWith |
P398
|
FINISHED |
| Object | nonprofit organizations in healthcare |
—
|
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: nonprofit organizations in healthcare | Statement: [Lynne Benioff, knownForWorkingWith, nonprofit organizations in healthcare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForWorkingWith Context triple: [Lynne Benioff, knownForWorkingWith, nonprofit organizations in healthcare]
-
A.
worksWith
chosen
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
B.
workedAs
Indicates that an entity held a particular job, role, or position, performing work in that capacity.
-
C.
associatedWork
Indicates that there exists a related or connected work (such as a publication, creative piece, or project) that is meaningfully linked to the subject.
-
D.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
E.
notablyAssociatedWith
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eac81c0c8190b3cb0d53b1cf62b5 |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94f049881908f10bb6548a8bb2e |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.