Triple
T9002094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVD |
E215060
|
entity |
| Predicate | storageCapacitySingleLayerDoubleSided |
P52985
|
FINISHED |
| Object | 9.4 GB |
—
|
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: 9.4 GB | Statement: [DVD, storageCapacitySingleLayerDoubleSided, 9.4 GB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storageCapacitySingleLayerDoubleSided Context triple: [DVD, storageCapacitySingleLayerDoubleSided, 9.4 GB]
-
A.
capacityPerSide
Indicates the maximum quantity or volume that each individual side or unit in a pair can hold or accommodate.
-
B.
diskSidesSupported
Indicates how many and which sides of a disk the system or device is capable of reading from or writing to.
-
C.
storageCapacity
chosen
Indicates the maximum amount of data or material that a storage entity can hold.
-
D.
tripleLayerCapacity
Indicates that something has the capacity or capability to function in or support three distinct layers or levels simultaneously.
-
E.
hasCapitalOnOneSide
Indicates that one entity has its capital city located on one side (e.g., bank, shore, border) of the other entity.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6956a6e08190bd3853a7c1c130eb |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:05 p.m.