Triple
T14660045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | If the World Was Ending |
E344212
|
entity |
| Predicate | hasPandemicCharityVersion |
P18107
|
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: [If the World Was Ending, hasPandemicCharityVersion, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPandemicCharityVersion Context triple: [If the World Was Ending, hasPandemicCharityVersion, yes]
-
A.
hasCharitableComponent
Indicates that something includes or is associated with a charitable element, such as donations, philanthropy, or support for a charitable cause.
-
B.
hasCharitySingle
Indicates that an entity is associated with exactly one specific charitable organization or charitable initiative.
-
C.
isCharity
Indicates that an entity operates as a charitable organization or is recognized as a charity.
-
D.
hasCharityConnection
Indicates a relationship in which one entity is connected to another through charitable activities, support, or affiliation.
-
E.
hasSpecialVersion
chosen
Indicates that an entity possesses or is associated with a distinct or customized version of another entity, differing from the standard or default form.
- 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.