Triple
T28544033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Krane |
E722378
|
entity |
| Predicate | roleAtGV |
P168974
|
FINISHED |
| Object | oversees investment strategy |
—
|
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: oversees investment strategy | Statement: [David Krane, roleAtGV, oversees investment strategy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtGV Context triple: [David Krane, roleAtGV, oversees investment strategy]
-
A.
roleAccordingTo
Indicates that an entity holds a particular role or function as defined or interpreted by a specified source or perspective.
-
B.
roleOn
Indicates that an entity holds or performs a specific role or function within another entity, context, or activity.
-
C.
roleOnGR20
Indicates the specific function or position an entity holds in the context of the GR20 (e.g., within an activity, project, or system labeled GR20).
-
D.
roleAtA24
Indicates that an entity holds or held a specific role or position at the organization or project referred to as A24.
-
E.
roleOfGroup
Indicates the function, responsibility, or position that a group holds within a broader context or structure.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 28, 2026, 3:37 a.m.