Triple
T321535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB Type-B |
E6424
|
entity |
| Predicate | counterpartConnector |
P6587
|
FINISHED |
| Object | USB Type-A |
—
|
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-A | Statement: [USB Type-B, counterpartConnector, USB Type-A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: counterpartConnector Context triple: [USB Type-B, counterpartConnector, USB Type-A]
-
A.
hasCounterpart
chosen
Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
-
B.
negotiatingParty
Indicates that an entity is actively involved as a participant in a negotiation process with another entity.
-
C.
coalitionPartnerWith
Indicates that two entities are formally aligned in a cooperative coalition, sharing goals or actions as partners within that coalition.
-
D.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
E.
formerPartner
Indicates that one entity was previously in a romantic or partnership relationship with another entity, but that relationship has since ended.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea81a1e88190b3496070eb3d85f5 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e948048c819098ba4de9261ef2ef |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.