Triple
T15355829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lego Bionicle |
E367166
|
entity |
| Predicate | revivalEnded |
P109066
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Lego Bionicle, revivalEnded, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivalEnded Context triple: [Lego Bionicle, revivalEnded, 2016]
-
A.
revivalEndTime
chosen
Indicates the point in time at which a revival process, event, or restored state comes to an end.
-
B.
revival
Indicates the act of bringing something back into use, popularity, or active existence after a period of decline, dormancy, or disuse.
-
C.
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.
-
D.
periodOfRevival
Indicates a time span during which something that had declined or been inactive experiences renewed growth, activity, or prominence.
-
E.
hasRevivalsIn
Indicates that something has been brought back, renewed, or reintroduced in specific times, places, or contexts.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e2c00648190ae2325e1ee58dcfd |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.