Triple
T37358886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Il mio tesoro |
E927525
|
entity |
| Predicate | historicalEraOfComposition |
P83770
|
FINISHED |
| Object | 1780s |
—
|
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: 1780s | Statement: [Il mio tesoro, historicalEraOfComposition, 1780s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEraOfComposition Context triple: [Il mio tesoro, historicalEraOfComposition, 1780s]
-
A.
actualHistoricalPeriodOfComposition
Indicates the specific historical period during which a work was actually composed, as opposed to when it is set, discovered, or later interpreted.
-
B.
historicalComposition
Indicates that one entity was historically part of, or contributed to the makeup or structure of, another entity during a past period.
-
C.
historical era
chosen
Indicates the broad historical period or epoch during which an entity, event, or phenomenon took place or is associated.
-
D.
historicalEraOfNaming
Indicates the historical era or time period during which an entity received its name.
-
E.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a01a0b63d148190b10206509c0a0a5b |
completed | May 11, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_6a01a0245d4c8190a3c3fbbe83f0389d |
completed | May 11, 2026, 9:23 a.m. |
Created at: May 3, 2026, 4:16 p.m.