Triple
T26897149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eternal winter |
E677925
|
entity |
| Predicate | triggeredDuring |
P3824
|
FINISHED |
| Object | Elsa's coronation day |
—
|
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: Elsa's coronation day | Statement: [Eternal winter, triggeredDuring, Elsa's coronation day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggeredDuring Context triple: [Eternal winter, triggeredDuring, Elsa's coronation day]
-
A.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
B.
occurredDuring
chosen
Indicates that one event or action took place within the temporal span of another event or time period.
-
C.
executedDuring
Indicates that an action or event was carried out within the temporal span of another specified event or period.
-
D.
triggeredFrom
Indicates that one event, action, or process was initiated or caused as a result of another specific event, action, or process.
-
E.
triggeredFires
Indicates that one entity caused or initiated the occurrence of one or more fires in another entity or location.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 5:48 a.m.