Triple
T8562306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCUMM |
E202717
|
entity |
| Predicate | supportsInterfaceStyle |
P1609
|
FINISHED |
| Object | point-and-click interface |
—
|
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: point-and-click interface | Statement: [SCUMM, supportsInterfaceStyle, point-and-click interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInterfaceStyle Context triple: [SCUMM, supportsInterfaceStyle, point-and-click interface]
-
A.
hasSystemStyle
Indicates that one entity is associated with, or characterized by, a particular system-defined style of another entity.
-
B.
supportsPartitionStyle
Indicates that one entity is compatible with or able to work with a specified partition style used by another entity.
-
C.
userInterfaceStyle
Indicates the visual presentation mode or theme (such as light or dark) that the user interface is currently using or configured to use.
-
D.
hasStyle
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
E.
hasContractStyle
Indicates that one entity is associated with or characterized by a particular contract style or contractual format.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe94c0c3c8190aca981c07b090dc0 |
completed | March 31, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:20 p.m.