Triple
T38455737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB 1.1 |
E912309
|
entity |
| Predicate | replacedLegacyInterface |
P11237
|
FINISHED |
| Object | RS-232 serial ports |
—
|
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: RS-232 serial ports | Statement: [USB 1.1, replacedLegacyInterface, RS-232 serial ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedLegacyInterface Context triple: [USB 1.1, replacedLegacyInterface, RS-232 serial ports]
-
A.
replacedInterface
chosen
Indicates that one interface has been substituted or superseded by another interface.
-
B.
replacedOnPlatformBy
Indicates that one entity has been superseded or taken over by another entity on a particular platform.
-
C.
replacedCapabilityOf
Indicates that one capability has taken the place of, or superseded, another capability.
-
D.
replacesSupportFor
Indicates that one entity takes over or substitutes for the role or function previously provided by another entity’s support.
-
E.
isConsideredLegacy
Indicates that something is regarded as outdated or superseded, typically maintained only for backward compatibility or historical reasons.
- 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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69feba0f09508190b3e871c62b19ec7f |
completed | May 9, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69feb957fe7c8190969fb31a6d1a59c8 |
completed | May 9, 2026, 4:34 a.m. |
Created at: May 3, 2026, 4:31 p.m.