Triple
T28583719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPlayer |
E723438
|
entity |
| Predicate | supportsScriptability |
P105398
|
FINISHED |
| Object | slave mode control |
—
|
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: slave mode control | Statement: [MPlayer, supportsScriptability, slave mode control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsScriptability Context triple: [MPlayer, supportsScriptability, slave mode control]
-
A.
canBeScripted
chosen
Indicates that the action or behavior can be defined, controlled, or automated through a script or scripting mechanism.
-
B.
hasScriptTool
Indicates that an entity uses, is associated with, or is supported by a particular scripting tool or scripting environment.
-
C.
usesScriptingLanguage
Indicates that an entity employs a scripting language to perform its operations, configuration, or automation tasks.
-
D.
supportsScriptVariant
Indicates that one entity is capable of handling, rendering, or operating with a particular variant of a script or writing system associated with another entity.
-
E.
supportsJavaScriptAPIs
Indicates that one entity provides or is compatible with JavaScript-based application programming interfaces for use by 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a0117b6539c8190be7d231e891fe546 |
completed | May 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_6a011762f7ec8190afc884b92419d33f |
completed | May 10, 2026, 11:40 p.m. |
Created at: April 28, 2026, 4:16 a.m.