Triple
T11507184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deathloop |
E272813
|
entity |
| Predicate | supportsMouseAndKeyboard |
P79785
|
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: [Deathloop, supportsMouseAndKeyboard, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMouseAndKeyboard Context triple: [Deathloop, supportsMouseAndKeyboard, true]
-
A.
supportsKeyboardAndMouse
chosen
Indicates that the subject provides compatibility with and can be operated using both a keyboard and a mouse.
-
B.
supportsKeyboard
Indicates that one entity is compatible with or able to be operated using a keyboard as an input method.
-
C.
supportsControllerInput
Indicates that an entity is capable of receiving and handling input from a controller device.
-
D.
supportsUserInteraction
Indicates that an entity enables or facilitates direct interaction with a user, such as receiving input or providing responsive feedback.
-
E.
hasKeyboard
Indicates that one entity possesses or is equipped with a keyboard as a component or accessory.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db43a648190be859bec2fe9f43b |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.