Triple
T21596032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chi è questa che vèn, ch’ogn’om la mira |
E532900
|
entity |
| Predicate | registro |
P144106
|
FINISHED |
| Object | elevato |
—
|
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: elevato | Statement: [Chi è questa che vèn, ch’ogn’om la mira, registro, elevato]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registro Context triple: [Chi è questa che vèn, ch’ogn’om la mira, registro, elevato]
-
A.
register
Indicates that an entity formally records or enrolls another entity or itself in an official system, list, or record.
-
B.
registrationFor
Indicates a relationship where one entity is enrolled, signed up, or formally recorded to participate in, use, or be associated with another entity (such as an event, service, or program).
-
C.
inscription
Indicates that text has been written, carved, or engraved onto a surface or object.
-
D.
registrationExample
Indicates that an instance serves as an illustrative or sample case of a particular registration.
-
E.
inscriptionBy
Indicates that an inscription was created, written, or carved by a particular agent or entity.
- 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.