Triple
T19659840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koovagam |
E472051
|
entity |
| Predicate | festivalParticipants |
P116079
|
FINISHED |
| Object | transgender women |
—
|
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: transgender women | Statement: [Koovagam, festivalParticipants, transgender women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festivalParticipants Context triple: [Koovagam, festivalParticipants, transgender women]
-
A.
festivalPresence
chosen
Indicates that an entity is present at, participates in, or is associated with a particular festival event.
-
B.
festivalActivity
Indicates that an entity is an event, performance, or engagement that takes place as part of a festival’s organized program.
-
C.
festivalAttracts
Indicates that a festival draws or brings in attendees, participants, or interest toward itself.
-
D.
festivalOrganiser
Indicates that one entity is responsible for planning, coordinating, or managing a festival for another entity or context.
-
E.
peerFestival
Indicates that two festivals are considered peers, sharing a comparable status, scale, or role within a given context.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6414993ac8190b6da3702b1924b24 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.