Triple
T11448157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dibiasky comet |
E271316
|
entity |
| Predicate | causesInStory |
P40708
|
FINISHED |
| Object | public panic |
—
|
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: public panic | Statement: [Dibiasky comet, causesInStory, public panic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causesInStory Context triple: [Dibiasky comet, causesInStory, public panic]
-
A.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
hasCauseNarrative
Indicates that one entity provides a narrative or explanatory account of the cause or causal background of another entity or event.
-
C.
stakesInStory
Indicates that one entity has a personal investment, risk, or potential gain/loss tied to the outcome of another entity’s story or narrative.
-
D.
narrativeConsequence
chosen
Indicates that one event, action, or state occurs as a direct result or outcome of another within a narrative sequence.
-
E.
debatedAsCauseOf
Indicates that one entity is discussed or argued over as a possible cause or origin of another entity.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d81c6d4890819082fb4a670feb2629 |
completed | April 9, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69d7e7162b288190a0bfb89f7eb747c7 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.