Triple
T30826950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HQ Trivia |
E785095
|
entity |
| Predicate | attemptedRevival |
P9802
|
FINISHED |
| Object | 2020-03 |
—
|
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: 2020-03 | Statement: [HQ Trivia, attemptedRevival, 2020-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptedRevival Context triple: [HQ Trivia, attemptedRevival, 2020-03]
-
A.
revivedAfter
Indicates that one entity comes back to life or is restored to a living or active state after a period of being dead, inactive, or nonfunctional, following another event or time point.
-
B.
returnInRevival
Indicates that an entity comes back or is brought back during a revival event or period.
-
C.
revivalUnder
Indicates that one entity is being brought back, renewed, or restored under the authority, influence, or auspices 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.
revival
chosen
Indicates the act of bringing something back into use, popularity, or active existence after a period of decline, dormancy, or disuse.
- 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:44 p.m.