Triple
T4757748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | terza rima |
E105628
|
entity |
| Predicate | typicalMeterInEnglish |
P58309
|
FINISHED |
| Object | iambic 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: iambic pentameter | Statement: [terza rima, typicalMeterInEnglish, iambic pentameter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMeterInEnglish Context triple: [terza rima, typicalMeterInEnglish, iambic pentameter]
-
A.
meterSystem
Indicates that one entity uses, is measured in, or is associated with a particular system of meters or measurement units.
-
B.
meter
Indicates a measurement relationship where one entity quantifies the length, distance, or extent of another in meters.
-
C.
metre
Indicates a measurement relationship where one entity’s length, distance, or size is quantified in units of metres.
-
D.
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.
-
E.
unitUK
Indicates that one entity uses or is measured in a unit of measure that is specific to or standard within the United Kingdom.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:20 p.m.