Triple
T14660054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | If the World Was Ending |
E344212
|
entity |
| Predicate | usesScenario |
P55686
|
FINISHED |
| Object | impending apocalypse |
—
|
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: impending apocalypse | Statement: [If the World Was Ending, usesScenario, impending apocalypse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesScenario Context triple: [If the World Was Ending, usesScenario, impending apocalypse]
-
A.
scenarioType
chosen
Indicates the specific category or kind of situation, context, or use case that an entity or event is associated with.
-
B.
variantScenario
Indicates a scenario that represents an alternative, modified, or derived version of another base scenario.
-
C.
usedInCase
Indicates that something (such as an item, method, or piece of information) is employed or applied within a particular case or instance.
-
D.
refersSituationTo
Indicates that one entity directs or assigns a situation, case, or matter to another entity for attention, handling, or further action.
-
E.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb51c84448190a1f5fa9ab8a1e2c4 |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.