Triple
T32757839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Diego Chargers (assistant coach) |
E837674
|
entity |
| Predicate | employerPeriod |
P125493
|
FINISHED |
| Object | 1961–2016 |
—
|
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: 1961–2016 | Statement: [San Diego Chargers (assistant coach), employerPeriod, 1961–2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employerPeriod Context triple: [San Diego Chargers (assistant coach), employerPeriod, 1961–2016]
-
A.
employerIn
Indicates that one entity serves as the employer of another within a specified context, such as a location, organization, or time period.
-
B.
employedAtTime
chosen
Indicates that an employment relationship holds during a specified time or time interval.
-
C.
employerSide
Indicates that the subject participates in or represents the employer’s position, interests, or perspective within an employment relationship or dispute.
-
D.
employerDuringUse
Indicates that one entity is the employer of another entity for the duration of a specified use, activity, or period.
-
E.
employer
Indicates a relationship where one entity hires, pays, and oversees the work of another entity.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: May 1, 2026, 1:13 a.m.