Triple
T29587764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Rose de l’infante |
E754068
|
entity |
| Predicate | workInCollectionType |
P2011
|
FINISHED |
| Object | historical-lyrical piece |
—
|
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: historical-lyrical piece | Statement: [La Rose de l’infante, workInCollectionType, historical-lyrical piece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workInCollectionType Context triple: [La Rose de l’infante, workInCollectionType, historical-lyrical piece]
-
A.
workCollectionTitle
Indicates the title assigned to a collection of works associated with an entity.
-
B.
workCollectedBy
Indicates that a created work has been gathered, acquired, or included within a collection maintained by another entity.
-
C.
basedOnWorkCollection
Indicates that something is derived from, adapted from, or otherwise created using a particular collection of works as its source or foundation.
-
D.
hasWorkInCollection
chosen
Indicates that a work or item is included as part of a particular collection.
-
E.
workTypeContributedTo
Indicates that an entity contributed to the creation, development, or production of a particular type of work.
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d7f46c481908cab81ff3be2b98b |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:12 p.m.