Triple
T372446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donna Zuckerberg |
E8295
|
entity |
| Predicate | roleAt |
P268
|
FINISHED |
| Object | founding editor-in-chief of Eidolon |
—
|
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: founding editor-in-chief of Eidolon | Statement: [Donna Zuckerberg, roleAt, founding editor-in-chief of Eidolon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAt Context triple: [Donna Zuckerberg, roleAt, founding editor-in-chief of Eidolon]
-
A.
role
chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
B.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
C.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
D.
definesRole
Indicates that one entity specifies or establishes the role, function, or position of another entity within a given context.
-
E.
identificationRole
Indicates that an entity serves as an identifier or plays a role in uniquely distinguishing or recognizing 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec018d508190b5687a9ba90b3092 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e960d880819084b3df4e5137a1e2 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.