Triple
T33175268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kallada River |
E849149
|
entity |
| Predicate | hasFestivalOnBank |
P3113
|
FINISHED |
| Object | Kallada Boat Race |
—
|
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: Kallada Boat Race | Statement: [Kallada River, hasFestivalOnBank, Kallada Boat Race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFestivalOnBank Context triple: [Kallada River, hasFestivalOnBank, Kallada Boat Race]
-
A.
hasFestival
chosen
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
-
B.
hasFestivalPeriod
Indicates that there is a specific time period during which a festival or celebratory event takes place.
-
C.
hasPublicHolidayOrFestival
Indicates that there exists a public holiday or festival associated with, occurring in, or relevant to the given entity.
-
D.
hasFestivalContext
Indicates that something is related to, occurs within, or is characterized by the setting, activities, or circumstances of a festival.
-
E.
hasFestivalConnection
Indicates a relationship in which two entities are connected through a festival, such as by participation, organization, sponsorship, or association with that event.
- 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_69f3495d06508190b0b7729982982cea |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:29 a.m.