Triple
T36737275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asclepiadean meter |
E907516
|
entity |
| Predicate | containsMetricalUnit |
P203229
|
FINISHED |
| Object | choriamb |
—
|
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: choriamb | Statement: [Asclepiadean meter, containsMetricalUnit, choriamb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMetricalUnit Context triple: [Asclepiadean meter, containsMetricalUnit, choriamb]
-
A.
hasUnitOf
Indicates that a quantity, measurement, or value is expressed in terms of a specific unit.
-
B.
isMetric
Indicates that something satisfies the properties required to be considered a metric, such as defining distances that obey non-negativity, identity, symmetry, and the triangle inequality.
-
C.
hasUnits
Indicates that a quantity, measurement, or value is expressed in a specified system or type of units.
-
D.
containsMeasure
Indicates that one entity includes or encompasses a specific measure or quantitative component as part of its content or structure.
-
E.
hasUnitIn
Indicates that one entity is contained or measured within another as a unit, specifying a unit-of-measure or component relationship.
- 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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a013e23698c81909a32d371b6f158d0 |
completed | May 11, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_6a013db04b108190985897aa6e95b4ec |
completed | May 11, 2026, 2:23 a.m. |
| PDg | Predicate description generation | batch_6a013e22bf3881909c8d7dc301966aa5 |
completed | May 11, 2026, 2:25 a.m. |
Created at: May 3, 2026, 4:12 p.m.