Triple
T10626684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild Hunt |
E250340
|
entity |
| Predicate | encounterConsequence |
P40708
|
FINISHED |
| Object | abduction |
—
|
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: abduction | Statement: [Wild Hunt, encounterConsequence, abduction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encounterConsequence Context triple: [Wild Hunt, encounterConsequence, abduction]
-
A.
hasConsequence
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
B.
narrativeConsequence
chosen
Indicates that one event, action, or state occurs as a direct result or outcome of another within a narrative sequence.
-
C.
announcedConsequence
Indicates that one entity has publicly stated or declared a specific outcome or consequence that will result from an action, event, or condition.
-
D.
impactOutcome
Indicates that one entity produces an effect or influence that changes the result, consequence, or final state of another entity or situation.
-
E.
hasConsequenceHypothesis
Indicates that one situation, event, or statement is hypothesized to lead to or imply a particular consequence.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df8207f08190a6362a8ba00988b2 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:55 p.m.