Triple
T25230211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badagu Thittu |
E632199
|
entity |
| Predicate | hasPerformanceTime |
P73837
|
FINISHED |
| Object | night-long performances |
—
|
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 performances | Statement: [Badagu Thittu, hasPerformanceTime, night-long performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformanceTime Context triple: [Badagu Thittu, hasPerformanceTime, night-long performances]
-
A.
performanceTime
chosen
Indicates the specific time or time interval at which a performance or event takes place.
-
B.
hasTypicalPerformanceDuration
Indicates the usual or expected length of time that a performance or activity typically lasts.
-
C.
hasPerformanceElement
Indicates that one entity includes, contains, or is associated with a specific performance-related component or element.
-
D.
hasPerformanceSchedule
Indicates that an entity has an associated timetable or plan specifying when its performances or shows are scheduled to occur.
-
E.
hasTimeOfAction
Indicates that an action is associated with a specific point or interval in time when it occurs.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 21, 2026, 1:04 p.m.