Triple
T6493326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenny Dillingham |
E148093
|
entity |
| Predicate | roleAtOregon |
P13957
|
FINISHED |
| Object | offensive coordinator |
—
|
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: offensive coordinator | Statement: [Kenny Dillingham, roleAtOregon, offensive coordinator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtOregon Context triple: [Kenny Dillingham, roleAtOregon, offensive coordinator]
-
A.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
B.
ordinationRole
Indicates the specific religious or ceremonial office, function, or capacity in which an entity is formally ordained.
-
C.
hasOrganizationalRole
chosen
Indicates that an entity holds a specific role, position, or function within an organization.
-
D.
roleAtMidway
Indicates that an entity holds or held a specific role, position, or function at the midpoint or intermediate stage of a process, event, or time period.
-
E.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
- 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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06ab6abbc8190a4971ad5a654b0cd |
completed | March 22, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69c06740bebc81909d9d6956baa2bcb9 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:53 p.m.