Triple
T25849370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ballad of the White Horse and Other Poems |
E651157
|
entity |
| Predicate | settingOfMainPoem |
P84255
|
FINISHED |
| Object | Anglo-Saxon England |
—
|
NE NERFINISHED |
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: Anglo-Saxon England | Statement: [The Ballad of the White Horse and Other Poems, settingOfMainPoem, Anglo-Saxon England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfMainPoem Context triple: [The Ballad of the White Horse and Other Poems, settingOfMainPoem, Anglo-Saxon England]
-
A.
hasPoemSetIn
chosen
Indicates that a poem is set in or takes place within a particular location or setting.
-
B.
hasFeatureInPoem
Indicates that a poem includes or is characterized by a particular feature, element, or attribute.
-
C.
hasCanonicalPoem
Indicates that an entity is associated with a poem recognized as its standard or authoritative version.
-
D.
poeticStructure
Indicates a relationship where one entity defines, embodies, or specifies the formal poetic organization (such as meter, rhyme scheme, or stanza pattern) used by another entity.
-
E.
containsPoem
Indicates that one entity includes or holds a poem as part of its contents.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 22, 2026, 7:58 a.m.