Triple
T1885089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM PC compatible |
E39944
|
entity |
| Predicate | hasKeyComponent |
P14613
|
FINISHED |
| Object | BIOS compatible with IBM PC BIOS |
—
|
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: BIOS compatible with IBM PC BIOS | Statement: [IBM PC compatible, hasKeyComponent, BIOS compatible with IBM PC BIOS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyComponent Context triple: [IBM PC compatible, hasKeyComponent, BIOS compatible with IBM PC BIOS]
-
A.
hasKeyElement
chosen
Indicates that one entity contains or depends on another entity that serves as a primary or essential component.
-
B.
hasKeyFunction
Indicates that one entity serves as a primary or essential function or role for another entity.
-
C.
hasKeyAspect
Indicates that something possesses a central, defining, or particularly important feature or characteristic.
-
D.
hasKeyResource
Indicates that an entity possesses or depends on a critical resource necessary for its function, operation, or success.
-
E.
hasKeyRelationship
Indicates a relationship where one entity serves as a key (e.g., identifier, access token, or primary reference) that grants access to, controls, or uniquely identifies 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_69a88633e4fc8190b7eb40463e048ec5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb4f53f408190ae30e1a12721e7d7 |
completed | March 7, 2026, 5:17 a.m. |
| PD | Predicate disambiguation | batch_69abafe497a88190a1da6af2888b71b4 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.