Triple
T25715159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clara et les Chics Types |
E644842
|
entity |
| Predicate | hasMusicalPerformance |
P43970
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Clara et les Chics Types, hasMusicalPerformance, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicalPerformance Context triple: [Clara et les Chics Types, hasMusicalPerformance, true]
-
A.
hasMusical
chosen
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
B.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
C.
performsMusicIn
Indicates that an entity presents or plays music within a particular venue, event, or context.
-
D.
performsMusicFrom
Indicates that one entity presents or executes a musical work that originates from or was created by another entity.
-
E.
hasMusicalForm
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 21, 2026, 9:38 p.m.