Triple
T27618349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barcarolle |
E700499
|
entity |
| Predicate | notableComposerOf |
P144230
|
FINISHED |
| Object | Jacques Offenbach |
—
|
NE NERFINISHED |
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: Jacques Offenbach | Statement: [Barcarolle, notableComposerOf, Jacques Offenbach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableComposerOf Context triple: [Barcarolle, notableComposerOf, Jacques Offenbach]
-
A.
notableComposerOfType
Indicates that an entity is a well-known or distinguished composer associated with a specified type, category, or genre of composition.
-
B.
hasMusicalComposer
Indicates that one entity serves as the musical composer responsible for creating the music associated with another entity.
-
C.
notableArtist
Indicates that the subject is an artist who is widely recognized or distinguished for their work.
-
D.
notableComposerRole
chosen
Indicates that the subject has a significant or distinguished role as a composer in relation to the object.
-
E.
notableMusician
Indicates that the subject is a musician who is widely recognized or distinguished for their musical work or impact.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_6a000014497c819088d5cda3977522dd |
completed | May 10, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69ffff9a52b08190be1024e0fb6fe661 |
completed | May 10, 2026, 3:46 a.m. |
Created at: April 27, 2026, 2:13 p.m.