Triple
T16890685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randolph Henry Ash |
E424161
|
entity |
| Predicate | hasPoeticWorks |
P107398
|
FINISHED |
| Object | fictional poems within "Possession" |
—
|
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: fictional poems within "Possession" | Statement: [Randolph Henry Ash, hasPoeticWorks, fictional poems within "Possession"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoeticWorks Context triple: [Randolph Henry Ash, hasPoeticWorks, fictional poems within "Possession"]
-
A.
hasWrittenPoetry
chosen
Indicates that an entity has created or authored one or more works of poetry.
-
B.
hasPoeticLyrics
Indicates that something (such as a song, text, or speech) contains lyrics or wording that are artistic, expressive, or characteristic of poetry.
-
C.
hasPoeticEpigraphs
Indicates that one entity (typically a work) includes poetic epigraphs associated with or prefacing another entity.
-
D.
hasPoemSetIn
Indicates that a poem is set in or takes place within a particular location or setting.
-
E.
containsPoemsBy
Indicates that one entity (such as a collection or publication) includes poems authored by 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbc473d4819090cfea374ef5ca49 |
completed | April 18, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.