Triple
T19628913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rokkasen |
E471212
|
entity |
| Predicate | typeOfPoetry |
P83256
|
FINISHED |
| Object | court 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: court poetry | Statement: [Rokkasen, typeOfPoetry, court poetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPoetry Context triple: [Rokkasen, typeOfPoetry, court poetry]
-
A.
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.
-
B.
poeticCategory
chosen
Indicates that one entity is classified as belonging to a particular poetic category or type of poetry in relation to another entity.
-
C.
poem
Indicates that one entity is a poem created, authored, or associated with another entity.
-
D.
hasPoemType
Indicates that an entity (such as a poem or literary work) is associated with or classified by a specific type or category of poem.
-
E.
poeticStyle
Indicates the stylistic or formal manner in which something is expressed in poetry, such as its structure, tone, and linguistic features.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641007e5881908da78e50aa36f340 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.