Triple
T28295865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorothy Kildall |
E713568
|
entity |
| Predicate | roleAtDigitalResearch |
P168621
|
FINISHED |
| Object | manager |
—
|
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: manager | Statement: [Dorothy Kildall, roleAtDigitalResearch, manager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtDigitalResearch Context triple: [Dorothy Kildall, roleAtDigitalResearch, manager]
-
A.
roleInResearch
Indicates that an entity participates in a research activity with a specified function, position, or responsibility within that research.
-
B.
researchOperator
Indicates that an entity conducts, manages, or is responsible for carrying out research activities on or for another entity.
-
C.
researchUser
Indicates that an entity conducts research on, studies, or investigates a particular user.
-
D.
roleInScholarlyCommunication
Indicates the function or position an entity holds within the processes of producing, evaluating, disseminating, or preserving scholarly work.
-
E.
usesResearchSubject
Indicates that one entity employs or utilizes another entity as a research subject in a study or investigation.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 27, 2026, 11:32 p.m.