Triple
T16882476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countdown to Armageddon |
E421453
|
entity |
| Predicate | hasLiveElements |
P35284
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Countdown to Armageddon, hasLiveElements, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveElements Context triple: [Countdown to Armageddon, hasLiveElements, yes]
-
A.
hasLivingComponents
Indicates that an entity includes or is composed of one or more living or biological components.
-
B.
hasSurvivingElement
Indicates that an entity retains at least one remaining or extant part, instance, or component that still exists.
-
C.
containsLiveAction
chosen
Indicates that something includes or features live-action content, typically involving real-world footage or live actors rather than solely animation or static media.
-
D.
hasLiveVersions
Indicates that an entity has one or more recorded or documented live-performance versions of itself.
-
E.
hasLivingParent
Indicates that an entity has at least one parent who is currently alive.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbbdffd8819093f1efd91f6d49dc |
completed | April 18, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.