Triple
T27666670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WAV |
E697244
|
entity |
| Predicate | typicalFileSizeCharacteristic |
P201359
|
FINISHED |
| Object | larger than compressed formats |
—
|
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: larger than compressed formats | Statement: [WAV, typicalFileSizeCharacteristic, larger than compressed formats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFileSizeCharacteristic Context triple: [WAV, typicalFileSizeCharacteristic, larger than compressed formats]
-
A.
typicalDimension
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
-
B.
typicalFileType
Indicates that one entity is the usual or commonly associated file type for the other entity.
-
C.
typicalFileFormat
Indicates the usual or standard file format typically associated with or used for a given entity or context.
-
D.
typicalUnitSize
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
-
E.
typicalPackSize
Indicates the usual quantity of items contained together in a single package for that entity.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ffed8912488190baa05f572e5b1b89 |
completed | May 10, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69ffed12a76c8190ad85c6ac869c72e9 |
completed | May 10, 2026, 2:27 a.m. |
| PDg | Predicate description generation | batch_69ffed884b908190b12422c790b1525e |
completed | May 10, 2026, 2:29 a.m. |
Created at: April 27, 2026, 2:38 p.m.