Triple
T4930316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compaq Portable |
E110677
|
entity |
| Predicate | systemBus |
P59538
|
FINISHED |
| Object | ISA |
—
|
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: ISA | Statement: [Compaq Portable, systemBus, ISA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemBus Context triple: [Compaq Portable, systemBus, ISA]
-
A.
systemBoard
Indicates a relationship where a system is associated with, mounted on, or implemented via a particular main circuit board (motherboard) that hosts its core components.
-
B.
system
Indicates that an entity functions as or belongs to a structured, organized set of components or processes that operate together as a system.
-
C.
systemEntry
Indicates that an entity is being recorded, registered, or introduced into a particular system or structured environment.
-
D.
systemType
Indicates the classification or category of a system that an entity belongs to or operates as.
-
E.
packageSystem
Indicates a relationship where an item or component is organized, bundled, or managed within a particular packaging or distribution system.
- 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_69bd4415190c8190817bee7ec9f9f944 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd703a0fa48190809b6ac3f2731349 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3695c8819094e7ad2f6d4ba1ac |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6d3806f881909c06687e9e57b67f |
completed | March 20, 2026, 3:52 p.m. |
Created at: March 20, 2026, 1:30 p.m.