Triple
T31645083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyagaraja Samadhi at Thiruvaiyaru |
E807563
|
entity |
| Predicate | eventNameVariant |
P31609
|
FINISHED |
| Object | Thiruvaiyaru Tyagaraja Aradhana |
—
|
NE NERFINISHED |
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: Thiruvaiyaru Tyagaraja Aradhana | Statement: [Tyagaraja Samadhi at Thiruvaiyaru, eventNameVariant, Thiruvaiyaru Tyagaraja Aradhana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventNameVariant Context triple: [Tyagaraja Samadhi at Thiruvaiyaru, eventNameVariant, Thiruvaiyaru Tyagaraja Aradhana]
-
A.
eventName
chosen
Indicates the specific label or title assigned to identify an event within a system or context.
-
B.
eventNameStyle
Indicates how the name of an event is formatted or styled in presentation or representation.
-
C.
eventRole
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
D.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
E.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 30, 2026, 10:50 p.m.