Triple
T4547480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Il Canzoniere |
E110080
|
entity |
| Predicate | metricalScheme |
P46136
|
FINISHED |
| Object | endecasillabo (hendecasyllabic verse) |
—
|
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: endecasillabo (hendecasyllabic verse) | Statement: [Il Canzoniere, metricalScheme, endecasillabo (hendecasyllabic verse)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metricalScheme Context triple: [Il Canzoniere, metricalScheme, endecasillabo (hendecasyllabic verse)]
-
A.
hasColourScheme
Indicates that an entity is associated with a particular set or pattern of colors used in its design or appearance.
-
B.
metricalFeature
chosen
Indicates a relationship where one entity specifies or characterizes a metrical property or pattern of another entity.
-
C.
symbolicStyle
Indicates that one entity employs or is characterized by a particular symbolic or emblematic style defined by the other entity.
-
D.
symbolDesigned
Indicates that one entity created or planned the design of a symbolic representation (such as a logo, icon, or emblem) for another entity.
-
E.
uniformStyle
Indicates that the related entities share the same or a consistent style, pattern, or formatting.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57f11f648190b20892cca6f617b1 |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:05 p.m.