Triple
T22798198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Sistema |
E564305
|
entity |
| Predicate | performanceComponent |
P111515
|
FINISHED |
| Object | public concerts |
—
|
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: public concerts | Statement: [El Sistema, performanceComponent, public concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceComponent Context triple: [El Sistema, performanceComponent, public concerts]
-
A.
performanceFeature
Indicates that an entity possesses a characteristic, capability, or attribute specifically related to its performance or operational effectiveness.
-
B.
performancePackage
Indicates that an entity is associated with a specific performance-related bundle or configuration, typically grouping features or enhancements that affect its performance.
-
C.
performanceModel
Indicates a relationship where one entity serves as a performance model that represents, predicts, or characterizes the performance behavior of another entity.
-
D.
performanceVariable
Indicates that one entity represents a measurable factor or parameter that influences or characterizes the performance of another entity.
-
E.
performanceWith
chosen
Indicates a relationship where two or more entities participate together in the same performance or staged presentation.
- 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cda76448190891c5190e1d75ae0 |
completed | April 29, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:30 p.m.