Triple
T28915775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamento |
E733357
|
entity |
| Predicate | hasWorkTitleType |
P186960
|
FINISHED |
| Object | descriptive title |
—
|
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: descriptive title | Statement: [Lamento, hasWorkTitleType, descriptive title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkTitleType Context triple: [Lamento, hasWorkTitleType, descriptive title]
-
A.
hasTitleWork
Indicates that an entity is associated with a specific work by its title (i.e., the entity has or bears that work’s title).
-
B.
hasWorkTitleElement
Indicates that an entity includes a specific textual component representing a work’s title or part of a work’s title.
-
C.
hasWorkTitleVariant
Indicates that an entity has an alternative or variant form of its work title, such as a different wording, spelling, or language version of the same title.
-
D.
hasWorkingTitle
Indicates that an entity is associated with a provisional or temporary title used during its development or production.
-
E.
hasWorkTitlePattern
Indicates that an entity’s work title follows or matches a specified pattern or structured format.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb2e9309fc81909dfefd9020d6fbad |
completed | May 6, 2026, 12:05 p.m. |
Created at: April 28, 2026, 8:14 a.m.