Triple
T32757840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Diego Chargers (assistant coach) |
E837674
|
entity |
| Predicate | employerPredecessorName |
P181274
|
FINISHED |
| Object | Los Angeles Chargers |
—
|
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: Los Angeles Chargers | Statement: [San Diego Chargers (assistant coach), employerPredecessorName, Los Angeles Chargers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employerPredecessorName Context triple: [San Diego Chargers (assistant coach), employerPredecessorName, Los Angeles Chargers]
-
A.
predecessorCompany
Indicates that one company previously existed in a role or form that was succeeded or replaced by another company.
-
B.
formerEmployer
Indicates that one entity previously employed the other but no longer does so.
-
C.
underlyingCompanyPredecessor
Indicates that one company served as a predecessor entity to another company in an underlying or foundational corporate relationship.
-
D.
predecessorCEO
Indicates that one person previously held the position of CEO before another specific person.
-
E.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: May 1, 2026, 1:13 a.m.