Triple
T29030512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macintosh System 2.1 |
E737713
|
entity |
| Predicate | supportsMouseInput |
P16220
|
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: [Macintosh System 2.1, supportsMouseInput, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMouseInput Context triple: [Macintosh System 2.1, supportsMouseInput, true]
-
A.
supportsKeyboardAndMouse
Indicates that the subject provides compatibility with and can be operated using both a keyboard and a mouse.
-
B.
hasMouse
chosen
Indicates that an entity possesses, uses, or is associated with a mouse (typically a computer pointing device or a small rodent).
-
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.
hasTouchControls
Indicates that an entity supports or is operated through touch-based input controls.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a02f441bd408190923b6b68adee8fde |
completed | May 12, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a02f3c1e64881908569423c9f298f26 |
completed | May 12, 2026, 9:32 a.m. |
Created at: April 28, 2026, 9:55 a.m.