Triple
T3281418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crossing the Water |
E68879
|
entity |
| Predicate | hasPoeticStyle |
P9652
|
FINISHED |
| Object | confessional 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: confessional poetry | Statement: [Crossing the Water, hasPoeticStyle, confessional poetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoeticStyle Context triple: [Crossing the Water, hasPoeticStyle, confessional poetry]
-
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.
hasLyricalStyle
chosen
Indicates that one entity possesses or is characterized by a particular lyrical style in relation to another entity or context.
-
C.
hasRhymeStyle
Indicates that two linguistic elements share the same pattern or style of rhyming.
-
D.
languageOfPoetry
Indicates that a specified language is the language in which a given piece of poetry is written or expressed.
-
E.
poeticStructure
Indicates a relationship where one entity defines, embodies, or specifies the formal poetic organization (such as meter, rhyme scheme, or stanza pattern) used 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb032d76c81909c568a4e56d12ce9 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.