Triple
T33467506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WOFF2 |
E857095
|
entity |
| Predicate | typicallySmallerThan |
P11452
|
FINISHED |
| Object | WOFF 1.0 files |
—
|
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: WOFF 1.0 files | Statement: [WOFF2, typicallySmallerThan, WOFF 1.0 files]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallySmallerThan Context triple: [WOFF2, typicallySmallerThan, WOFF 1.0 files]
-
A.
smallerThan
chosen
Indicates that one entity has a strictly lesser size, dimension, or magnitude than another entity.
-
B.
isSmall
Indicates that one entity has a size that is relatively small, either in absolute terms or compared to a reference standard or another entity.
-
C.
isSmallestOf
Indicates that an entity has the minimum size or value within a specified set or group of entities.
-
D.
narrowerThan
Indicates that one entity has a smaller width or breadth than another entity.
-
E.
canHaveSmallerSize
Indicates that one entity is capable of having a smaller size than another entity or than its own current or typical size.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:37 a.m.