Triple
T21596021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chi è questa che vèn, ch’ogn’om la mira |
E532900
|
entity |
| Predicate | metro |
P144104
|
FINISHED |
| Object | endecasillabo |
—
|
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 | Statement: [Chi è questa che vèn, ch’ogn’om la mira, metro, endecasillabo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metro Context triple: [Chi è questa che vèn, ch’ogn’om la mira, metro, endecasillabo]
-
A.
metropolitan
Indicates that a location is part of, belongs to, or lies within a specified metropolitan (urban) area.
-
B.
metropole
Indicates a relationship where one place functions as the principal or most important city or center of activity for another place or region.
-
C.
metroLineInaugurated
Indicates that a metro line was officially opened and began operation on a specific date or during a specific event.
-
D.
metropolitanSee
Indicates a relationship where one metropolitan area views, oversees, or conceptually regards another place, entity, or aspect within its sphere of influence.
-
E.
metropolitanSeeTakenFrom
Indicates that a view or image of a metropolitan area is captured from a particular vantage point or location.
- 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_69e0c46251648190876f0427cf2d321b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eefae15a7c819081627450ae726b0b |
completed | April 27, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e63384a8fc819084c596bb53a3a1db |
completed | April 20, 2026, 2:09 p.m. |
Created at: April 16, 2026, 6:32 p.m.