Triple
T425284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB Mini-B |
E8193
|
entity |
| Predicate | contactType |
P12914
|
FINISHED |
| Object | surface-mount contacts in receptacle |
—
|
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: surface-mount contacts in receptacle | Statement: [USB Mini-B, contactType, surface-mount contacts in receptacle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contactType Context triple: [USB Mini-B, contactType, surface-mount contacts in receptacle]
-
A.
associatedNumber
Indicates a relationship where a specific number is linked or assigned to an entity as its associated value.
-
B.
hasContactType
chosen
Indicates the specific kind or category of contact relationship that exists between two entities.
-
C.
appointmentMethod
Indicates how an appointment is arranged, such as the channel, process, or means used to schedule it.
-
D.
addressType
Indicates the specific kind or category of address associated with an entity (e.g., home, work, billing, or shipping).
-
E.
officeNumber
Indicates the specific room or suite number assigned to an office within a building or complex.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eed56ab481909eec289075496260 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd6736c81909a6ca549f77b4345 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.