Triple
T576787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Assistant |
E13773
|
entity |
| Predicate | languageSupport |
P11734
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Google Assistant, languageSupport, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageSupport Context triple: [Google Assistant, languageSupport, English]
-
A.
languageProvision
chosen
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
B.
languageBranch
Indicates that one language belongs to, or is classified under, a broader linguistic branch or subgroup.
-
C.
languageVariant
Indicates that one language is a variant, dialect, or localized form of another language.
-
D.
languageFeature
Indicates that one entity is a characteristic, property, or capability of a language associated with the other entity.
-
E.
recognizedLanguage
Indicates that an entity has identified, detected, or acknowledged a particular language as being used or present.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b68cc808190b1ba45bdad78443d |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c692288190b88f30299516b5ba |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.