Triple
T29030513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macintosh System 2.1 |
E737713
|
entity |
| Predicate | supportsKeyboardInput |
P98894
|
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, supportsKeyboardInput, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsKeyboardInput Context triple: [Macintosh System 2.1, supportsKeyboardInput, true]
-
A.
supportsKeyboard
chosen
Indicates that one entity is compatible with or able to be operated using a keyboard as an input method.
-
B.
supportsKeyboardAndMouse
Indicates that the subject provides compatibility with and can be operated using both a keyboard and a mouse.
-
C.
hasKeyboard
Indicates that one entity possesses or is equipped with a keyboard as a component or accessory.
-
D.
supportsControllerInput
Indicates that an entity is capable of receiving and handling input from a controller device.
-
E.
hasKeyboardBy
Indicates that an entity is equipped with or uses a keyboard provided, installed, or controlled 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a02f847b9848190a9fedbc411ae0918 |
completed | May 12, 2026, 9:52 a.m. |
| PD | Predicate disambiguation | batch_6a02f556860c8190b2995433fa05fdd0 |
completed | May 12, 2026, 9:39 a.m. |
Created at: April 28, 2026, 9:55 a.m.