Triple
T32541724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Media Creation Tool |
E831729
|
entity |
| Predicate | supportsLanguageSelection |
P57998
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Media Creation Tool, supportsLanguageSelection, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLanguageSelection Context triple: [Media Creation Tool, supportsLanguageSelection, true]
-
A.
usesLanguageSupport
Indicates that one entity makes use of language-related assistance, features, or services provided by another entity.
-
B.
supportsLanguageOverrides
chosen
Indicates that an entity allows its default behavior or settings to be modified based on specific language selections or preferences.
-
C.
secondaryLanguageSupport
Indicates that an entity provides assistance, services, or functionality in an additional (non-primary) language.
-
D.
usesLanguageFor
Indicates that an entity employs a particular language as a tool or medium to perform some activity, function, or purpose.
-
E.
mayUseLanguagesOf
Indicates that an entity is permitted to use the languages associated with another entity.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:02 a.m.