Triple
T16430008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EBM |
E399046
|
entity |
| Predicate | eraOfRevival |
P48377
|
FINISHED |
| Object | late 1990s |
—
|
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: late 1990s | Statement: [EBM, eraOfRevival, late 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfRevival Context triple: [EBM, eraOfRevival, late 1990s]
-
A.
periodOfRevival
chosen
Indicates a time span during which something that had declined or been inactive experiences renewed growth, activity, or prominence.
-
B.
revival
Indicates the act of bringing something back into use, popularity, or active existence after a period of decline, dormancy, or disuse.
-
C.
revivedBy
Indicates that an entity has been brought back to life, consciousness, or active state through the action or intervention of another entity.
-
D.
revivedAs
Indicates that an entity, after having ceased to exist or function in its original form, comes back into existence or operation in a new or restored form.
-
E.
revivalYear
Indicates the year in which something (such as a work, practice, or institution) was brought back into active use or renewed after a period of decline or inactivity.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328fe0f488190ac34aa677c980a20 |
completed | April 18, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.