Triple
T165474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netflix, Inc. |
E3004
|
entity |
| Predicate | hasLanguageAvailability |
P2177
|
FINISHED |
| Object | multiple 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 languages | Statement: [Netflix, Inc., hasLanguageAvailability, multiple languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageAvailability Context triple: [Netflix, Inc., hasLanguageAvailability, multiple languages]
-
A.
hasLanguageGroup
Indicates that an entity belongs to, is associated with, or is categorized under a particular language group.
-
B.
isLanguageOf
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
-
C.
hasTranslation
Indicates that one entity is a translation or translated version of another entity in a different language.
-
D.
includesLanguage
chosen
Indicates that one entity contains, supports, or makes use of a specified language as part of its content, functionality, or representation.
-
E.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a25883ac8481909616b2179561bd98 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a25664ba8081908ac298511a9fc5ba |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.