Triple
T33355075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul |
E854049
|
entity |
| Predicate | connectedToArtForm |
P29303
|
FINISHED |
| Object | 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: opera | Statement: [Paul, connectedToArtForm, opera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToArtForm Context triple: [Paul, connectedToArtForm, 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.
associatedWithWorkOfArt
Indicates a relationship in which an entity is connected or related to a specific work of art, such as through creation, contribution, ownership, or contextual association.
-
C.
hasArtisticAssociationWith
Indicates a relationship in which two entities are connected through shared, collaborative, or thematically related artistic work or influence.
-
D.
hasArtworksIntegratedWith
Indicates that one entity incorporates or embeds artworks within or as part of another entity.
-
E.
artForm
Indicates the type or category of artistic expression that characterizes or defines something (e.g., painting, music, dance).
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: May 1, 2026, 1:34 a.m.