Triple
T36663754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB 1.0 |
E905201
|
entity |
| Predicate | supportsBulkTransfers |
P204989
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [USB 1.0, supportsBulkTransfers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBulkTransfers Context triple: [USB 1.0, supportsBulkTransfers, true]
-
A.
supportsBatchProcessing
Indicates that the subject can handle multiple items or tasks in a single grouped operation rather than processing them individually.
-
B.
supportsTransportOver
Indicates that one entity provides the necessary means or infrastructure for another entity to carry out transportation or data transfer over it.
-
C.
supportsTransactions
Indicates that one entity provides the capability for another entity to perform or manage transactions reliably.
-
D.
supportsExchangeBetween
Indicates that one entity enables or facilitates the exchange or transfer of something (e.g., data, value, or resources) between two or more other entities.
-
E.
supportsBatchSize
Indicates that one entity can handle or is compatible with processing multiple items together in a single batch of a specified size.
- F. None of above. chosen
Provenance (4 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:12 p.m.