Triple
T8570675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaypro computers |
E202916
|
entity |
| Predicate | portabilityMethod |
P83695
|
FINISHED |
| Object | carrying handle |
—
|
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: carrying handle | Statement: [Kaypro computers, portabilityMethod, carrying handle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portabilityMethod Context triple: [Kaypro computers, portabilityMethod, carrying handle]
-
A.
isPortable
Indicates that an object can be easily moved or carried from one place to another without significant effort or setup.
-
B.
isPortableComparedTo
Indicates that one entity can be moved, carried, or transported more easily than another entity.
-
C.
isLessPortableThan
Indicates that one entity is more difficult to move, carry, or transport than another entity.
-
D.
mobilizationMethod
Indicates the method or process by which resources, people, or assets are organized and activated for a particular purpose or operation.
-
E.
portedTo
Indicates that something has been adapted or transferred from its original environment or platform to run or function on a different one.
- F. None of above. chosen
Provenance (4 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_69ca8327b0a881908606ff860713964d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea4223888190a56d9026ae0b9ec0 |
completed | March 31, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30e37ac8190b685df36274602b5 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:21 p.m.