Triple
T31945162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuit d’ivresse et d’extase infinie |
E815629
|
entity |
| Predicate | parentWorkType |
P190504
|
FINISHED |
| Object | grand opera |
—
|
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: grand opera | Statement: [Nuit d’ivresse et d’extase infinie, parentWorkType, grand opera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentWorkType Context triple: [Nuit d’ivresse et d’extase infinie, parentWorkType, grand opera]
-
A.
parentWorkTitle
Indicates that the value is the title of a larger or original work of which the current item is a part, adaptation, or derivative.
-
B.
parentWorksAt
Indicates that the parent of a given person is employed at a specified organization or workplace.
-
C.
parentOccupation
Indicates that one entity has an occupation which is the job or profession of the other entity’s parent.
-
D.
roleInFatherWork
Indicates that one entity has a specific role or involvement in the work or professional activities of another entity identified as the father.
-
E.
parentWorkSignificance
Indicates the degree of importance or influence that a parent work has on the related work or context.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcc7779d248190afdb348a95375443 |
completed | May 7, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
| PDg | Predicate description generation | batch_69fcc73264e08190b0b5917f32226fae |
completed | May 7, 2026, 5:09 p.m. |
Created at: May 1, 2026, 12:06 a.m.