Triple
T33203606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB Type-C Alternate Mode architecture |
E849967
|
entity |
| Predicate | repurposes |
P47023
|
FINISHED |
| Object | USB Type-C high-speed data lanes |
—
|
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: USB Type-C high-speed data lanes | Statement: [USB Type-C Alternate Mode architecture, repurposes, USB Type-C high-speed data lanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repurposes Context triple: [USB Type-C Alternate Mode architecture, repurposes, USB Type-C high-speed data lanes]
-
A.
laterRepurposedFor
chosen
Indicates that something was originally used for one purpose and subsequently assigned a different, new purpose.
-
B.
reimagines
Indicates that one entity creatively reconceives, interprets, or presents another in a significantly new or different way.
-
C.
reusedIn
Indicates that something previously used in one context or instance is used again in another context or instance.
-
D.
relocatedForPurpose
Indicates that an entity moved from one location to another specifically to fulfill or pursue a particular purpose or objective.
-
E.
reconstructs
Indicates performing an action to rebuild, restore, or reassemble something from its parts, damage, or prior state.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.