Triple
T32757866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Diego Chargers (assistant coach) |
E837674
|
entity |
| Predicate | franchiseFounded |
P46462
|
FINISHED |
| Object | 1960 |
—
|
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: 1960 | Statement: [San Diego Chargers (assistant coach), franchiseFounded, 1960]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: franchiseFounded Context triple: [San Diego Chargers (assistant coach), franchiseFounded, 1960]
-
A.
foundedFranchise
Indicates that an entity established or created a particular franchise.
-
B.
foundedAsFranchiseYear
chosen
Indicates the year in which an entity was established specifically as a franchise.
-
C.
franchiseStart
Indicates the point in time or event at which a franchise or franchising relationship is initiated or begins.
-
D.
franchiseDebut
Indicates the first appearance or introduction of an entity within a particular franchise or series.
-
E.
appliedToFranchiseFoundedIn
Indicates that something (such as a rule, policy, or action) is applied specifically to a franchise that was founded in a particular time or place.
- 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_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:13 a.m.