Triple
T1200673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soundgarden |
E25772
|
entity |
| Predicate | reformedInYear |
P9113
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Soundgarden, reformedInYear, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reformedInYear Context triple: [Soundgarden, reformedInYear, 2010]
-
A.
reformedOffice
Indicates that an office or official position has been reorganized, restructured, or fundamentally changed from its previous form.
-
B.
denominationReform
Indicates a change or restructuring in a religious denomination’s doctrines, practices, or organizational form.
-
C.
reformDate
Indicates the date on which a reform, change, or restructuring officially took effect or was implemented.
-
D.
reestablishedInYear
chosen
Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
-
E.
refoundedBy
Indicates that an entity was re-established or reconstituted by another entity after a period of inactivity, dissolution, or significant change.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd9ec3488190afe35af54efae5e9 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5ed2b88190aab992913957e1cf |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.