Triple
T37847985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falstaff (libretto) |
E943957
|
entity |
| Predicate | placeOfFirstPublicationOfAssociatedScore |
P13815
|
FINISHED |
| Object | Milan |
—
|
NE NERFINISHED |
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: Milan | Statement: [Falstaff (libretto), placeOfFirstPublicationOfAssociatedScore, Milan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfFirstPublicationOfAssociatedScore Context triple: [Falstaff (libretto), placeOfFirstPublicationOfAssociatedScore, Milan]
-
A.
placeOfFirstPublication
chosen
Indicates the location where a work was first published or made publicly available.
-
B.
firstPublicationIn
Indicates the initial venue, medium, or context in which a work was first published.
-
C.
firstPublicationOfContainingWork
Indicates that the related entity is the earliest published work in which the referenced work or content first appeared.
-
D.
firstAssociatedPublicationYear
Indicates the calendar year in which an entity’s earliest associated publication was first released or made publicly available.
-
E.
initialPublication
Indicates the relationship in which a work is first formally published or made publicly available.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: May 3, 2026, 4:19 p.m.