Triple
T36687253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurigalu Saar Kurigalu |
E905850
|
entity |
| Predicate | workTitleInScript |
P186166
|
FINISHED |
| Object | ಕುರಿಗಳು ಸಾರ್ ಕುರಿಗಳು |
—
|
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: ಕುರಿಗಳು ಸಾರ್ ಕುರಿಗಳು | Statement: [Kurigalu Saar Kurigalu, workTitleInScript, ಕುರಿಗಳು ಸಾರ್ ಕುರಿಗಳು]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workTitleInScript Context triple: [Kurigalu Saar Kurigalu, workTitleInScript, ಕುರಿಗಳು ಸಾರ್ ಕುರಿಗಳು]
-
A.
workTitle
Indicates the formal title or name of a work (such as a book, artwork, or composition) associated with an entity.
-
B.
workTitleIn
Indicates that one entity is the title of a work (e.g., book, film, artwork) that appears within or is contained in another entity.
-
C.
workTitleInLatinScript
Indicates that the title of a work is expressed using a Latin-based writing system.
-
D.
workTitleType
Indicates the specific category or type of a work’s title (e.g., main title, alternative title, translated title) in relation to that work.
-
E.
workTitleOfCharacter
Indicates that the specified work (e.g., book, film, game) is the title in which the given character appears.
- F. None of above. chosen
Provenance (4 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:12 p.m.