Triple
T29101332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OPN2 |
E736645
|
entity |
| Predicate | hasNotableChipImplementation |
P102
|
FINISHED |
| Object | YM2612 |
—
|
NE NERFINISHED |
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: YM2612 | Statement: [OPN2, hasNotableChipImplementation, YM2612]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableChipImplementation Context triple: [OPN2, hasNotableChipImplementation, YM2612]
-
A.
hasChipType
Indicates that an entity is associated with or uses a specific type or category of chip.
-
B.
hasOnChip
Indicates that one component or system includes another component integrated directly onto the same chip or integrated circuit.
-
C.
requiresSupportChips
Indicates that an entity depends on or needs additional support components (chips) in order to function or be used properly.
-
D.
hasNotableImplementationAt
chosen
Indicates that something has a significant or noteworthy implementation located at or associated with a particular place, context, or platform.
-
E.
hasOnChipOscillator
Indicates that one entity incorporates or is equipped with an oscillator circuit integrated directly on its chip.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: April 28, 2026, 11:12 a.m.