Triple
T34568169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Winnowing Winds |
E887548
|
entity |
| Predicate | hasCommonEnglishTitle |
P205471
|
FINISHED |
| Object | The Winnowing Winds |
E887548
|
NE 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: The Winnowing Winds | Statement: [The Winnowing Winds, hasCommonEnglishTitle, The Winnowing Winds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonEnglishTitle Context triple: [The Winnowing Winds, hasCommonEnglishTitle, The Winnowing Winds]
-
A.
hasTitleInEnglishOrthography
Indicates that an entity has a specific title expressed using English spelling and writing conventions.
-
B.
hasApproximateEnglishTitle
Indicates that an entity is associated with an English title that is an approximate or non-exact rendering of its original title.
-
C.
hasCommonTitle
Indicates that two or more entities share the same title or designation.
-
D.
hasTitleInModernEnglish
Indicates that an entity is associated with a specific title expressed in modern English.
-
E.
hasTitleInLanguage
Indicates that an entity has a specific title expressed in a particular language.
- F. None of above. chosen
Provenance (5 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3741034cfc8190941a530c4e5eba02 |
completed | June 21, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 2:02 a.m.