Triple
T29132406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solitude entonnoir |
E738414
|
entity |
| Predicate | hasPoeticElements |
P60474
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Solitude entonnoir, hasPoeticElements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoeticElements Context triple: [Solitude entonnoir, hasPoeticElements, true]
-
A.
hasPoeticLyrics
Indicates that something (such as a song, text, or speech) contains lyrics or wording that are artistic, expressive, or characteristic of poetry.
-
B.
hasPoeticDevice
chosen
Indicates that one entity (typically a text or passage) employs or contains a specific poetic device present in the other entity.
-
C.
hasPoeticSpeaker
Indicates that one entity functions as the poetic speaker or voice expressing the content of another entity (such as a poem or lyrical work).
-
D.
hasPoeticAttestations
Indicates that the subject is documented or evidenced in poetic sources or literary works.
-
E.
hasPoeticVoice
Indicates that one entity possesses or exhibits the distinctive poetic style, tone, or expressive voice associated with 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: April 28, 2026, 11:32 a.m.