Triple
T32557856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Elephant Whisperers |
E832138
|
entity |
| Predicate | platformLanguageOption |
P11734
|
FINISHED |
| Object | multiple languages via subtitles |
—
|
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 languages via subtitles | Statement: [The Elephant Whisperers, platformLanguageOption, multiple languages via subtitles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformLanguageOption Context triple: [The Elephant Whisperers, platformLanguageOption, multiple languages via subtitles]
-
A.
plateLanguage
Indicates that a license plate is written in, or associated with, a particular language.
-
B.
languageProvision
chosen
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
C.
possibleLanguage
Indicates that an entity could plausibly be expressed, interpreted, or communicated in a given language.
-
D.
navigationLanguage
Indicates the language used for navigation-related content, such as menus, directions, or interface controls.
-
E.
languageOfCommand
Indicates that a specified language is the one in which a given command is expressed or issued.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:03 a.m.