Triple
T16037377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeff Tedford |
E389002
|
entity |
| Predicate | roleAtWashingtonState |
P121700
|
FINISHED |
| Object | offensive assistant |
—
|
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 assistant | Statement: [Jeff Tedford, roleAtWashingtonState, offensive assistant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtWashingtonState Context triple: [Jeff Tedford, roleAtWashingtonState, offensive assistant]
-
A.
roleAtVirginia
Indicates that an entity holds or held a specific role or position at an institution or organization in Virginia.
-
B.
roleAtD.C.United
Indicates that an entity holds or held a specific role or position within the D.C. United soccer organization.
-
C.
ethnicRole
Indicates a role, function, or social position that is specifically associated with or defined by an entity’s ethnicity.
-
D.
roleInStateFormation
Indicates that an entity played a contributing role in the process of establishing, consolidating, or transforming a state or political entity.
-
E.
roleInFederalism
Indicates the specific function, authority, or responsibility an entity holds within a federal system of divided and shared governance.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1ff5cd7e481908a29214139a3de2e |
completed | April 17, 2026, 9:37 a.m. |
Created at: April 10, 2026, 4:56 a.m.