Triple
T27295877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerome Eugene Morrow |
E688762
|
entity |
| Predicate | roleInGattacaCorporation |
P192755
|
FINISHED |
| Object | genetic donor for an employee |
—
|
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: genetic donor for an employee | Statement: [Jerome Eugene Morrow, roleInGattacaCorporation, genetic donor for an employee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInGattacaCorporation Context triple: [Jerome Eugene Morrow, roleInGattacaCorporation, genetic donor for an employee]
-
A.
roleInElysium
Indicates that an entity holds a specific role, position, or function within the context of Elysium.
-
B.
roleInGemini3
Indicates that an entity holds a specific role or function within the Gemini 3 mission or project.
-
C.
roleAtAnthropic
Indicates that an entity holds or held a specific role or position at Anthropic.
-
D.
roleInGemini10
Indicates that an entity holds a specific role or position in the context of the Gemini 10 mission or project.
-
E.
protagonistWorksFor
Indicates that the protagonist is employed by or under the authority of another entity (such as a person, organization, or group).
- F. None of above. chosen
Provenance (4 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
| PDg | Predicate description generation | batch_69fd2a2095f88190bfcbcb2973516ffc |
completed | May 8, 2026, 12:11 a.m. |
Created at: April 27, 2026, 11:18 a.m.