Triple
T30107752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poem 85 (Odi et amo) |
E765176
|
entity |
| Predicate | originalMeterSecondLine |
P201719
|
FINISHED |
| Object | pentameter |
—
|
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: pentameter | Statement: [Poem 85 (Odi et amo), originalMeterSecondLine, pentameter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalMeterSecondLine Context triple: [Poem 85 (Odi et amo), originalMeterSecondLine, pentameter]
-
A.
originalMeterFirstLine
Indicates that the first line of a text is written in the original metrical pattern or verse form.
-
B.
finalLineMeter
Indicates that the metrical pattern or structure of the final line of a text, verse, or utterance is being specified or characterized.
-
C.
secondInLine
Indicates that one entity occupies the second position in a sequence or queue immediately following the first.
-
D.
hasMeter
Indicates that one entity possesses, uses, or is associated with a specific meter (a measuring device or metrical pattern).
-
E.
meteringSystem
Indicates that one entity functions as a metering system used to measure, record, or regulate quantities or usage related to another entity.
- F. None of above. chosen
Provenance (4 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0018cf6ebc8190aee6288788d0067e |
completed | May 10, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_6a001855e8588190a65840485473cf8b |
completed | May 10, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_6a0018cebf688190bbd90ac79d250182 |
completed | May 10, 2026, 5:34 a.m. |
Created at: April 29, 2026, 7:09 p.m.