Triple
T25235858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oo Antava Oo Oo Antava |
E632333
|
entity |
| Predicate | hasAlternateLanguageVersions |
P35567
|
FINISHED |
| Object | multiple Indian languages |
—
|
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: multiple Indian languages | Statement: [Oo Antava Oo Oo Antava, hasAlternateLanguageVersions, multiple Indian languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternateLanguageVersions Context triple: [Oo Antava Oo Oo Antava, hasAlternateLanguageVersions, multiple Indian languages]
-
A.
hasBilingualVersions
Indicates that something exists in two different language versions or forms.
-
B.
hasLanguages
chosen
Indicates that an entity is associated with one or more languages it uses, supports, or is expressed in.
-
C.
hasRelatedLanguage
Indicates that one language is related to another through shared linguistic origins, features, or classification.
-
D.
isMultilingual
Indicates that an entity can understand and/or communicate in multiple languages.
-
E.
hasAlternativeNameOfParentLanguage
Indicates that an entity has an alternative or variant name derived from or associated with the name of its parent language.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 1:07 p.m.