Triple
T23246091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silvae |
E581584
|
entity |
| Predicate | alternateInterpretationOfTitle |
P151522
|
FINISHED |
| Object | improvised pieces |
—
|
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: improvised pieces | Statement: [Silvae, alternateInterpretationOfTitle, improvised pieces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternateInterpretationOfTitle Context triple: [Silvae, alternateInterpretationOfTitle, improvised pieces]
-
A.
haveAlternativeTitle
Indicates that an entity is known by one or more alternative titles or names in addition to its primary title.
-
B.
alternateWorkingTitle
Indicates that one title serves as an alternative working title for the same work or project as another title.
-
C.
hasAlternativeEditionTitle
Indicates that an entity has a different or variant title used in another edition of the same work.
-
D.
hasAlternateTitleRegion
Indicates that an entity has an alternate title that is specifically used or valid within a particular geographic region.
-
E.
alternateTitleOfAdaptedEdition
Indicates that a title is an alternative title specifically for an adapted edition of a work, rather than for the original version.
- 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193f0f5d88190a497f14601f9bf29 |
completed | April 29, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:10 p.m.