Triple
T34161386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wildes Heer |
E876284
|
entity |
| Predicate | witnessConsequence |
P812
|
FINISHED |
| Object | risk of being swept into the hunt |
—
|
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: risk of being swept into the hunt | Statement: [Wildes Heer, witnessConsequence, risk of being swept into the hunt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: witnessConsequence Context triple: [Wildes Heer, witnessConsequence, risk of being swept into the hunt]
-
A.
hasConsequence
chosen
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
B.
consequenceOfInfluence
Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
-
C.
consequenceInText
Indicates that one event, action, or state is presented in the text as a consequence or result of another.
-
D.
witnesses
Indicates that one entity observes an event, action, or situation involving another entity, typically as a bystander or observer.
-
E.
announcedConsequence
Indicates that one entity has publicly stated or declared a specific outcome or consequence that will result from an action, event, or condition.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fdedf708190ab68c2d567e086d0 |
completed | May 3, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.