Triple
T18671534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Inchcape Rock |
E456486
|
entity |
| Predicate | hasStanzaicStructure |
P30317
|
FINISHED |
| Object | regular stanzas |
—
|
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: regular stanzas | Statement: [The Inchcape Rock, hasStanzaicStructure, regular stanzas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStanzaicStructure Context triple: [The Inchcape Rock, hasStanzaicStructure, regular stanzas]
-
A.
hasTotalSyllableCountPerStanza
Indicates that a stanza is associated with the total number of syllables it contains.
-
B.
hasSyllableStructure
Indicates that an entity (typically a word or morpheme) possesses a particular arrangement or pattern of syllables.
-
C.
hasSyllabicStructure
Indicates that an entity possesses a specific arrangement or pattern of syllables, such as their number, order, or type.
-
D.
poeticStructure
chosen
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.
-
E.
hasRhymeSchemeFeature
Indicates that a poetic work exhibits a specific characteristic or pattern related to its rhyme scheme.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556b21d2481908e1b8b583bfabb72 |
completed | April 19, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.