Triple
T34594995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donald Stufft |
E888284
|
entity |
| Predicate | contributedToProject |
P152794
|
FINISHED |
| Object | pip |
—
|
NE NERFINISHED |
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: pip | Statement: [Donald Stufft, contributedToProject, pip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contributedToProject Context triple: [Donald Stufft, contributedToProject, pip]
-
A.
contributedToProgram
Indicates that an entity played a role in creating, supporting, or participating in a particular program.
-
B.
hasProgrammingContribution
chosen
Indicates that an entity has made a contribution to the development, improvement, or maintenance of a programming-related artifact, project, or activity.
-
C.
hasContributionFrom
Indicates that something (such as a work, project, or outcome) is created, influenced, or supported in part by a specified contributor.
-
D.
hasProject
Indicates that an entity is associated with or responsible for a particular project.
-
E.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
Created at: May 1, 2026, 2:03 a.m.