Triple
T34702712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sara Haines |
E1000416
|
entity |
| Predicate | roleOnProgram |
P165140
|
FINISHED |
| Object | contributor on Today |
—
|
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: contributor on Today | Statement: [Sara Haines, roleOnProgram, contributor on Today]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOnProgram Context triple: [Sara Haines, roleOnProgram, contributor on Today]
-
A.
roleOn
chosen
Indicates that an entity holds or performs a specific role or function within another entity, context, or activity.
-
B.
roleOnPern
Indicates the specific function, position, or duty an entity holds within the context of Pern.
-
C.
roleInAppointments
Indicates the specific function or capacity an entity holds within one or more scheduled appointments.
-
D.
roleAtGV
Indicates that an entity holds or held a specific role or position at a particular organization, institution, or venue referred to as GV.
-
E.
roleInSection106
Indicates that an entity has a specific role or involvement within the context of Section 106 (typically of a legal or regulatory framework).
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 3:59 p.m.