Triple
T21079637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Follower |
E519327
|
entity |
| Predicate | oftenAnthologizedIn |
P31760
|
FINISHED |
| Object | modern poetry anthologies |
—
|
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: modern poetry anthologies | Statement: [Follower, oftenAnthologizedIn, modern poetry anthologies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenAnthologizedIn Context triple: [Follower, oftenAnthologizedIn, modern poetry anthologies]
-
A.
isFrequentlyAnthologized
chosen
Indicates that a work is often selected and included in multiple anthologies or collected editions.
-
B.
notableAnthologyEdited
Indicates that an entity has served as the editor of a notable anthology involving another entity.
-
C.
numberInAnthology
Indicates the specific position or sequence number that a work occupies within an anthology.
-
D.
containsPoemsFrom
Indicates that one entity includes or features poems that originate from or are authored in association with another entity.
-
E.
literaryCollection
Indicates that one entity is a collection or compilation of literary works that includes or is associated with the other 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e702d939e08190a37d7b7cc1872ad5 |
completed | April 21, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:49 p.m.