Triple
T34161365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wildes Heer |
E876284
|
entity |
| Predicate | hasFunctionInFolklore |
P95054
|
FINISHED |
| Object | omen of 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: omen of war | Statement: [Wildes Heer, hasFunctionInFolklore, omen of war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFunctionInFolklore Context triple: [Wildes Heer, hasFunctionInFolklore, omen of war]
-
A.
folkloreFunction
chosen
Indicates that something serves a role, purpose, or function within a body of folklore, such as myths, legends, or traditional narratives.
-
B.
hasFolkloreStatus
Indicates that something is recognized or classified as having a status or role within folklore or traditional cultural narratives.
-
C.
hasFictionalFunction
Indicates that an entity serves a role, purpose, or function within a fictional context or narrative.
-
D.
includesFolklore
Indicates that one entity contains, incorporates, or features folklore as part of its content or composition.
-
E.
countryOfFolklore
Indicates the country with which a particular piece or tradition of folklore is associated or from which it originates.
- 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_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:54 a.m.