Triple
T33057420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MICKEY 2.0 |
E845878
|
entity |
| Predicate | implementationPlatform |
P1292
|
FINISHED |
| Object | ASIC |
—
|
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: ASIC | Statement: [MICKEY 2.0, implementationPlatform, ASIC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementationPlatform Context triple: [MICKEY 2.0, implementationPlatform, ASIC]
-
A.
deploymentPlatformType
Indicates the type or category of platform on which a deployment is executed or hosted.
-
B.
implementationTarget
Indicates that one entity serves as the concrete implementation or realization of another entity’s specification, interface, or design.
-
C.
implementationType
Indicates the specific manner or approach by which something is implemented or realized in practice.
-
D.
adoptedPlatformOn
Indicates that an entity began using or officially adopted a particular platform on a specific date or point in time.
-
E.
platforms
chosen
Indicates that one entity provides or serves as a base, medium, or environment that supports the operation, distribution, or presentation of 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_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:25 a.m.