Triple
T9002109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVD |
E215060
|
entity |
| Predicate | supportsInteractiveMenus |
P85660
|
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: [DVD, supportsInteractiveMenus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInteractiveMenus Context triple: [DVD, supportsInteractiveMenus, true]
-
A.
supportsInteractiveWidgets
Indicates that an entity is capable of handling or enabling interactive widgets within its context or environment.
-
B.
supportsUserInteraction
Indicates that an entity enables or facilitates direct interaction with a user, such as receiving input or providing responsive feedback.
-
C.
supportsKeyboardAndMouse
Indicates that the subject provides compatibility with and can be operated using both a keyboard and a mouse.
-
D.
hasInteractiveActivity
Indicates that an entity includes or is associated with an activity that requires active user participation or engagement.
-
E.
supportsControllerInput
Indicates that an entity is capable of receiving and handling input from a controller device.
- F. None of above. chosen
Provenance (4 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6956a6e08190bd3853a7c1c130eb |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:05 p.m.