Triple
T32463444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poems and Ballads |
E829637
|
entity |
| Predicate | inCollectionSeries |
P123565
|
FINISHED |
| Object | Poems and Ballads series |
—
|
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: Poems and Ballads series | Statement: [Poems and Ballads, inCollectionSeries, Poems and Ballads series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inCollectionSeries Context triple: [Poems and Ballads, inCollectionSeries, Poems and Ballads series]
-
A.
inCollectionPerspective
Indicates that an entity is viewed or interpreted from the standpoint or framing of a particular collection or set it belongs to.
-
B.
coreSeries
Indicates that one entity is the primary or central series to which another related work or set of works belongs.
-
C.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
D.
seriesBy
Indicates that one entity is the creator, author, or originator of a series to which the other entity belongs.
-
E.
seriesWith
chosen
Indicates that one entity is part of, or grouped together in, the same series or sequence as another entity.
- 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_69f3491ee87c81908cbf5890079c2af6 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c34f15c88190a2cf86631d80ae35 |
completed | May 3, 2026, 3:38 a.m. |
| PD | Predicate disambiguation | batch_69f6ba700a708190ab6db62791e43774 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:57 a.m.