Triple
T31506319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cadre Noir |
E803824
|
entity |
| Predicate | performsPublicShows |
P173400
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Cadre Noir, performsPublicShows, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsPublicShows Context triple: [Cadre Noir, performsPublicShows, yes]
-
A.
hasPublicPerformances
chosen
Indicates that an entity conducts or is involved in performances that are open and accessible to the general public.
-
B.
presentsPerformancesBy
Indicates that one entity organizes or stages performances that feature or are carried out by another entity.
-
C.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
D.
hasPublicEventsIn
Indicates that an entity organizes or holds public events within a specified location or context.
-
E.
hasNotableLivePerformancesBy
Indicates that an entity (such as a work, event, or venue) is associated with notable live performances given by a specified performer or group.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: April 30, 2026, 9:47 p.m.