Triple
T21442438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Betamax |
E528969
|
entity |
| Predicate | cassetteDimensions |
P67473
|
FINISHED |
| Object | 15.6 cm × 9.6 cm × 2.5 cm |
—
|
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: 15.6 cm × 9.6 cm × 2.5 cm | Statement: [Betamax, cassetteDimensions, 15.6 cm × 9.6 cm × 2.5 cm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cassetteDimensions Context triple: [Betamax, cassetteDimensions, 15.6 cm × 9.6 cm × 2.5 cm]
-
A.
cassetteWidth
Indicates the measurement of how wide a cassette is along its horizontal dimension.
-
B.
cassetteHeight
Indicates the vertical dimension or elevation associated with a cassette relative to a reference point or system.
-
C.
cassetteTypeSupported
Indicates that a given system, device, or component is compatible with and can operate using a specified cassette type.
-
D.
cartridge
Indicates that one entity is a cartridge associated with, contained in, or used by another entity.
-
E.
typicalDimension
chosen
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b70322bc8190ae693163ededf5a0 |
completed | April 22, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:05 p.m.