Triple
T22782759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Champabai |
E563881
|
entity |
| Predicate | characterInPlayLanguage |
P71694
|
FINISHED |
| Object | Marathi |
—
|
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: Marathi | Statement: [Champabai, characterInPlayLanguage, Marathi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterInPlayLanguage Context triple: [Champabai, characterInPlayLanguage, Marathi]
-
A.
isCharacterInWorkLanguage
chosen
Indicates that a character appears in a work (e.g., book, film, game) in a specific language version or localization.
-
B.
characterInPlayBy
Indicates that a character appears in or is part of a play authored or created by a specific person.
-
C.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
D.
hasLanguageCharacter
Indicates that an entity uses, contains, or is associated with a specific written or symbolic character from a language.
-
E.
languageCharacterizedBy
Indicates that a language is defined or distinguished by a particular feature, property, or characteristic.
- 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c2ee4e88190951afb2abe69009f |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:29 p.m.