Triple
T2088814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gordon and Betty Moore Foundation |
E32617
|
entity |
| Predicate | hasKeyPersonRole |
P256
|
FINISHED |
| Object | president |
—
|
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: president | Statement: [Gordon and Betty Moore Foundation, hasKeyPersonRole, president]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyPersonRole Context triple: [Gordon and Betty Moore Foundation, hasKeyPersonRole, president]
-
A.
hasOrganizationalRole
Indicates that an entity holds a specific role, position, or function within an organization.
-
B.
keyPerson
chosen
Indicates that a person plays a primary, central, or critically important role in relation to an organization, project, or entity.
-
C.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
D.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
E.
hasCapitalRole
Indicates that an entity holds an official role, function, or status specifically associated with a capital city.
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba712388819091d68a4bb99f6b17 |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b4356881909217c42ccb8bb1ed |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.