Triple
T29211510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palamedu |
E740556
|
entity |
| Predicate | sportsCategoryOfEvent |
P1907
|
FINISHED |
| Object | traditional rural sport |
—
|
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: traditional rural sport | Statement: [Palamedu, sportsCategoryOfEvent, traditional rural sport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportsCategoryOfEvent Context triple: [Palamedu, sportsCategoryOfEvent, traditional rural sport]
-
A.
sportsCategory
Indicates that one entity is classified as a type or category within the domain of sports to which the other entity belongs.
-
B.
sportCategory
chosen
Indicates that one entity is classified as a type or category of sport to which the other entity (typically a specific sport or sporting event) belongs.
-
C.
sportEventType
Indicates the specific kind or category of sport associated with a given sporting event.
-
D.
sportEvent
Indicates a relationship where an entity is involved in, associated with, or characterizes a competitive or organized sporting event.
-
E.
sportEventTypeOrganized
Indicates that an entity organizes or is responsible for arranging a specific type of sports 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 12:11 p.m.