Triple
T9661742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Wind |
E233605
|
entity |
| Predicate | highlightsAttributeOf |
P89469
|
FINISHED |
| Object | Enlil as powerful storm god |
—
|
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: Enlil as powerful storm god | Statement: [Lord Wind, highlightsAttributeOf, Enlil as powerful storm god]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highlightsAttributeOf Context triple: [Lord Wind, highlightsAttributeOf, Enlil as powerful storm god]
-
A.
highlights
Indicates that one entity draws special attention to, emphasizes, or visually marks another entity as important or noteworthy.
-
B.
isMajorHighlightOf
Indicates that something serves as a primary or especially notable feature, event, or focal point within a larger context or whole.
-
C.
emphasizesAttributeOfHermes
Indicates that something highlights or draws special attention to a particular attribute or characteristic of Hermes.
-
D.
coreAttribute
Indicates that one attribute is a fundamental, defining, or essential property of another entity.
-
E.
themeHighlights
Indicates that certain elements are emphasized or visually distinguished as key features within a particular theme.
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0b7728819099473f404382b26a |
completed | April 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:14 p.m.