Triple
T25020592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odi barbare |
E626558
|
entity |
| Predicate | usesMetricalForm |
P82742
|
FINISHED |
| Object | classical Latin metres |
—
|
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: classical Latin metres | Statement: [Odi barbare, usesMetricalForm, classical Latin metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMetricalForm Context triple: [Odi barbare, usesMetricalForm, classical Latin metres]
-
A.
dominantMetreOf
Indicates that one metre (rhythmic pattern) is the primary or prevailing metrical structure used in another work, passage, or musical/poetic context.
-
B.
writtenInMetre
chosen
Indicates that a piece of writing is composed using a specific metrical pattern or rhythmic structure.
-
C.
hasScalarForm
Indicates that something possesses or can be represented in a single-valued (scalar) form rather than as a vector, matrix, or more complex structure.
-
D.
metricForm
Indicates that one entity is expressed or represented in a particular metric form or measurement format relative to another.
-
E.
hasMusicalForm
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 6:06 a.m.