Triple
T28298485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adriana Lecouvreur (Adriana) |
E713634
|
entity |
| Predicate | operaSourceWork |
P45645
|
FINISHED |
| Object | play Adrienne Lecouvreur |
—
|
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: play Adrienne Lecouvreur | Statement: [Adriana Lecouvreur (Adriana), operaSourceWork, play Adrienne Lecouvreur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operaSourceWork Context triple: [Adriana Lecouvreur (Adriana), operaSourceWork, play Adrienne Lecouvreur]
-
A.
workFromOpera
Indicates that an entity performs work or operates starting from, or based in, an opera-related context or location.
-
B.
operaAct
Indicates that an entity performs in or takes part in an act (segment) of an opera performance.
-
C.
cataloguedWithOpera
Indicates that an item is recorded or documented in association with a specific opera work or opera-related cataloging system.
-
D.
hasSourceWork
chosen
Indicates that something originates from, is derived from, or is based on a particular source work.
-
E.
operaComponent
Indicates that one entity is a constituent part or section of an opera associated with the other entity.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: April 27, 2026, 11:33 p.m.