Triple
T10626644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild Hunt |
E250340
|
entity |
| Predicate | consideredOmenOf |
P95053
|
FINISHED |
| Object | war |
—
|
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: war | Statement: [Wild Hunt, consideredOmenOf, war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredOmenOf Context triple: [Wild Hunt, consideredOmenOf, war]
-
A.
functionInOmens
Indicates that something serves as a function, role, or operative element within the system, practice, or interpretation of omens.
-
B.
prophetAmong
Indicates that one entity serves as a prophet within, or in relation to, a particular group, community, or people represented by the other entity.
-
C.
considered
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
-
D.
subjectOfProphecy
Indicates that the subject is foretold or predicted to play a significant role or experience a specific event according to a prophecy.
-
E.
interpretedAsProphecyBy
Indicates that something (such as an event, statement, or sign) is understood or treated by someone as a prophecy or predictive message about the future.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69d6df463ea8819091d6683e476b4f21 |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 8:55 p.m.