Triple
T6968621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yakshagana |
E161548
|
entity |
| Predicate | performanceTime |
P73837
|
FINISHED |
| Object | night-long |
—
|
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: night-long | Statement: [Yakshagana, performanceTime, night-long]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceTime Context triple: [Yakshagana, performanceTime, night-long]
-
A.
performanceMeasurement
Indicates the act of assessing, quantifying, or evaluating how well an entity, process, or system performs against defined criteria or objectives.
-
B.
performance
Indicates that one entity’s effectiveness, quality, or success in carrying out a task, function, or role is being evaluated or characterized in relation to some standard or expectation.
-
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.
calculationTime
Indicates the amount of time required to perform or complete a calculation.
-
E.
performanceTuningBy
Indicates that an entity’s performance has been adjusted, optimized, or fine-tuned by another entity.
- F. None of above. chosen
Provenance (4 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db152b2081909271493a5d1469fb |
completed | March 27, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d9bb57e88190a3a7cec34e3b617f |
completed | March 27, 2026, 7:25 p.m. |
Created at: March 27, 2026, 2:30 p.m.