Triple
T4545436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snowman |
E110034
|
entity |
| Predicate | survivalContext |
P21744
|
FINISHED |
| Object | global pandemic aftermath |
—
|
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: global pandemic aftermath | Statement: [Snowman, survivalContext, global pandemic aftermath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivalContext Context triple: [Snowman, survivalContext, global pandemic aftermath]
-
A.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
B.
survivedEvent
Indicates that an entity continued to live or exist after experiencing and not being destroyed or killed by a particular event.
-
C.
survivesIn
chosen
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
-
D.
survivesAs
Indicates that one entity continues to exist or persist in place of, or after the end or transformation of, another entity.
-
E.
survivorTerm
Indicates that one entity is designated as the surviving or remaining party in relation to another entity, often after a loss, termination, or adverse event.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57d62a8481909d5d803a582c76a1 |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:05 p.m.