Triple
T29042564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greek lyric poetry |
E738036
|
entity |
| Predicate | usesMetricalForms |
P82742
|
FINISHED |
| Object | varied metrical schemes |
—
|
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: varied metrical schemes | Statement: [Greek lyric poetry, usesMetricalForms, varied metrical schemes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMetricalForms Context triple: [Greek lyric poetry, usesMetricalForms, varied metrical schemes]
-
A.
hasLyricalForm
Indicates that one entity (typically a musical or poetic work) possesses or is characterized by a particular lyrical structure or form.
-
B.
hasMusicalForm
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
-
C.
usesSyllables
Indicates that one entity forms, expresses, or analyzes something by employing syllables as its basic units.
-
D.
writtenInMetre
chosen
Indicates that a piece of writing is composed using a specific metrical pattern or rhythmic structure.
-
E.
dominantMetreOf
Indicates that one metre (rhythmic pattern) is the primary or prevailing metrical structure used in another work, passage, or musical/poetic context.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 28, 2026, 10:02 a.m.