Triple
T425280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB Mini-B |
E8193
|
entity |
| Predicate | introducedEra |
P8259
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [USB Mini-B, introducedEra, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedEra Context triple: [USB Mini-B, introducedEra, early 2000s]
-
A.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
-
B.
introducedDuring
chosen
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other entity.
-
C.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
-
D.
introducedInCentury
Indicates the century during which something (such as an idea, technology, practice, or entity) was first introduced or came into use.
-
E.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
- 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.