Triple
T20593322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Younger Dryas impact hypothesis |
E505986
|
entity |
| Predicate | claimsCauseOf |
P116397
|
FINISHED |
| Object | onset of Younger Dryas cooling |
—
|
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: onset of Younger Dryas cooling | Statement: [Younger Dryas impact hypothesis, claimsCauseOf, onset of Younger Dryas cooling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimsCauseOf Context triple: [Younger Dryas impact hypothesis, claimsCauseOf, onset of Younger Dryas cooling]
-
A.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
causeOfClaim
chosen
Indicates the underlying reason, event, or condition that gives rise to a particular claim.
-
C.
eligibleCause
Indicates that one entity qualifies as a valid or acceptable cause or reason for another entity or outcome.
-
D.
causeStatus
Indicates that one entity brings about, initiates, or is responsible for a particular state or condition in another entity.
-
E.
causeInStory
Indicates that one event, action, or state functions as the cause of another within the narrative structure of a story.
- 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a97d63cc8190853e052d5930470d |
completed | April 20, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.