Triple
T4796463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The White Election |
E106723
|
entity |
| Predicate | usesPoeticText |
P36572
|
FINISHED |
| Object | 19th-century American poetry |
—
|
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: 19th-century American poetry | Statement: [The White Election, usesPoeticText, 19th-century American poetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPoeticText Context triple: [The White Election, usesPoeticText, 19th-century American poetry]
-
A.
usedByPoet
Indicates that something (such as a word, style, device, or object) is employed or utilized by a poet.
-
B.
hasPoeticLyrics
chosen
Indicates that something (such as a song, text, or speech) contains lyrics or wording that are artistic, expressive, or characteristic of poetry.
-
C.
languageOfPoetry
Indicates that a specified language is the language in which a given piece of poetry is written or expressed.
-
D.
readPoemAt
Indicates that an entity reads or performs a poem at a specific time, place, or event.
-
E.
associatedWithPoem
Indicates a relationship in which an entity is connected or linked to a particular poem, such as by authorship, subject, reference, or contextual association.
- 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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6b40c29c8190adab3503f8ba0145 |
completed | March 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69bd622f88188190a51d52ccfad3d2dd |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.