Triple
T19285487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compaq Armada 1500 series |
E482297
|
entity |
| Predicate | typicalInputDevice |
P2571
|
FINISHED |
| Object | built-in keyboard |
—
|
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: built-in keyboard | Statement: [Compaq Armada 1500 series, typicalInputDevice, built-in keyboard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalInputDevice Context triple: [Compaq Armada 1500 series, typicalInputDevice, built-in keyboard]
-
A.
inputDevice
chosen
Indicates that one entity functions as a device used to provide input to another entity or system.
-
B.
inputType
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
C.
typicalServerDevice
Indicates that the subject is a device that is commonly or characteristically used as a server in typical scenarios.
-
D.
peripheralType
Indicates the specific category or kind of peripheral device associated with or used by an entity.
-
E.
testedDeviceType
Indicates that one entity is the type or category of device on which another entity has been tested.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc0152d48190b92272d4c7caa708 |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.