Triple
T26680273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parineeta |
E672585
|
entity |
| Predicate | hasAdaptationLanguage |
P121206
|
FINISHED |
| Object | Hindi |
—
|
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: Hindi | Statement: [Parineeta, hasAdaptationLanguage, Hindi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdaptationLanguage Context triple: [Parineeta, hasAdaptationLanguage, Hindi]
-
A.
adaptedInLanguage
chosen
Indicates that a work or content has been modified or translated so it can be presented or understood in a specified language.
-
B.
hasAdaptationsIn
Indicates that something possesses or exhibits adaptations within a particular context, environment, or domain.
-
C.
hasAdaptationStrategy
Indicates that an entity employs or is associated with a specific method or approach for adapting to changing conditions or requirements.
-
D.
hasAdaptationRoleIn
Indicates that an entity serves a specific adaptation-related role or function within another entity, process, or context.
-
E.
hasSubtitles
Indicates that one media item provides subtitle text or tracks that accompany another media item or its audio content.
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 3:19 a.m.