Triple
T9183403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega Genesis Model 3 |
E220389
|
entity |
| Predicate | hasAudioChip |
P32170
|
FINISHED |
| Object | Yamaha FM-based sound (Genesis-compatible) |
—
|
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: Yamaha FM-based sound (Genesis-compatible) | Statement: [Sega Genesis Model 3, hasAudioChip, Yamaha FM-based sound (Genesis-compatible)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAudioChip Context triple: [Sega Genesis Model 3, hasAudioChip, Yamaha FM-based sound (Genesis-compatible)]
-
A.
audioChip
chosen
Indicates that one entity functions as, or contains, an audio processing chip in relation to another entity.
-
B.
hasAudioFeature
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
-
C.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
D.
soundChip
Indicates that one entity functions as or contains the sound-processing chip used by another entity.
-
E.
hasSoundSystem
Indicates that an entity is equipped with or includes a sound system as one of its features.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc31734908190b8ebe3b57849ca5f |
completed | April 1, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:24 p.m.