Triple
T25179136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WAGN |
E630534
|
entity |
| Predicate | franchiseRestructuredIn |
P158002
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [WAGN, franchiseRestructuredIn, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: franchiseRestructuredIn Context triple: [WAGN, franchiseRestructuredIn, 2004]
-
A.
franchiseChange
Indicates a change in the ownership, control, or branding rights of a franchise from one party to another.
-
B.
franchiseRenamedAs
Indicates that an existing franchise has changed its official name to a new one.
-
C.
franchiseShift
Indicates a change or transfer in control, ownership, or primary association of a franchise from one party or context to another.
-
D.
franchiseEventuallyBecame
Indicates that one franchise transformed into, was succeeded by, or ultimately came to be identified as another franchise over time.
-
E.
replacedFranchiseLocationOf
Indicates that one franchise location has taken the place of, or succeeded, another franchise location in a given context or territory.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46dc2ac088190a629119847b6097e |
completed | May 1, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 12:35 p.m.