Triple
T391247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB Micro-B |
E8884
|
entity |
| Predicate | wasIntroducedFor |
P3018
|
FINISHED |
| Object | space-constrained mobile devices |
—
|
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: space-constrained mobile devices | Statement: [USB Micro-B, wasIntroducedFor, space-constrained mobile devices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasIntroducedFor Context triple: [USB Micro-B, wasIntroducedFor, space-constrained mobile devices]
-
A.
introducedFor
chosen
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
B.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
-
C.
introducedDuring
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other entity.
-
D.
introducedAfter
Indicates that one entity was introduced at a later time or stage than another entity.
-
E.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec5d73e881909101308a583c8f13 |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e96960608190bdd342da9c5ddb5e |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.