Triple
T32406746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Promessi Sposi |
E828103
|
entity |
| Predicate | firstCompleteEditionTitle |
P206266
|
FINISHED |
| Object | I Promessi Sposi |
E828103
|
NE 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: I Promessi Sposi | Statement: [I Promessi Sposi, firstCompleteEditionTitle, I Promessi Sposi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCompleteEditionTitle Context triple: [I Promessi Sposi, firstCompleteEditionTitle, I Promessi Sposi]
-
A.
firstCompleteEditionPublisher
Indicates the publisher responsible for issuing the first complete edition of a work.
-
B.
firstReleaseTitle
Indicates the title associated with an entity’s initial or earliest release.
-
C.
completedAsFirstEdition
Indicates that an entity was completed in its initial or original edition, before any subsequent versions or revisions.
-
D.
firstKnownPublicationTitle
Indicates the title of the earliest known publication associated with an entity.
-
E.
firstEditionType
Indicates that an entity is classified as a first edition of a work, specifying the type or category of that first edition.
- F. None of above. chosen
Provenance (5 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a344f19d5148190824eaf0a09d4f2fd |
completed | June 18, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:53 a.m.