Triple
T21151428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LWV 49 |
E521197
|
entity |
| Predicate | associatedArtisticForm |
P29303
|
FINISHED |
| Object | French Baroque 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: French Baroque opera | Statement: [LWV 49, associatedArtisticForm, French Baroque opera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedArtisticForm Context triple: [LWV 49, associatedArtisticForm, French Baroque opera]
-
A.
associatedWithArtForm
chosen
Indicates a relationship where an entity is connected or linked to a particular art form, such as by practice, creation, representation, or influence.
-
B.
artisticField
Indicates the artistic domain or creative discipline in which an entity is active or associated.
-
C.
traditionalArtForm
Indicates that something is an established artistic practice or style that has been handed down through cultural or historical tradition.
-
D.
artSpecialty
Indicates that an entity’s primary focus, expertise, or specialization is in a particular art form or artistic domain.
-
E.
hasArtisticDiscipline
Indicates that one entity practices, specializes in, or is associated with a particular artistic discipline or field.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72401830c8190a2008c40c4174d97 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:58 p.m.