Triple
T33057400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MICKEY 2.0 |
E845878
|
entity |
| Predicate | hasKeySize |
P118977
|
FINISHED |
| Object | 80 bits |
—
|
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: 80 bits | Statement: [MICKEY 2.0, hasKeySize, 80 bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeySize Context triple: [MICKEY 2.0, hasKeySize, 80 bits]
-
A.
hasSize
Indicates that one entity possesses a particular physical magnitude or extent, such as length, volume, or overall dimensions.
-
B.
hasKeyQuantity
Indicates that an entity is associated with a primary or defining quantity that characterizes or measures it.
-
C.
hasKeyNumber
Indicates that an entity is associated with a specific key identifier or reference number used to distinguish or access it.
-
D.
hasKeyStructure
Indicates that one entity possesses or defines the primary structural framework or core structural pattern of another entity.
-
E.
hasKeyDimension
chosen
Indicates that one entity possesses or defines a primary, essential dimension or parameter that characterizes 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 1:25 a.m.