Triple
T25296657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerala chenda melam |
E634233
|
entity |
| Predicate | performanceScale |
P51866
|
FINISHED |
| Object | large ensemble |
—
|
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: large ensemble | Statement: [Kerala chenda melam, performanceScale, large ensemble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceScale Context triple: [Kerala chenda melam, performanceScale, large ensemble]
-
A.
scoreScale
Indicates the scale or range on which a score or rating is expressed or measured.
-
B.
performanceBasis
Indicates that one entity’s performance is evaluated, determined, or justified on the basis of another specified factor, standard, or reference.
-
C.
performanceClass
chosen
Indicates the category or level of performance to which an entity is assigned, typically reflecting its capabilities or quality tier.
-
D.
performanceWith
Indicates a relationship where two or more entities participate together in the same performance or staged presentation.
-
E.
performanceVariable
Indicates that one entity represents a measurable factor or parameter that influences or characterizes the performance of another entity.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 21, 2026, 1:22 p.m.