Triple
T29182021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2149 |
E739767
|
entity |
| Predicate | hasEnvelopeResolution |
P33931
|
FINISHED |
| Object | 16-bit period value |
—
|
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: 16-bit period value | Statement: [Yamaha YM2149, hasEnvelopeResolution, 16-bit period value]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnvelopeResolution Context triple: [Yamaha YM2149, hasEnvelopeResolution, 16-bit period value]
-
A.
hasEnvelopeShapes
Indicates that one entity possesses or is characterized by specific envelope-like shapes associated with another entity.
-
B.
hasResolution
chosen
Indicates that one entity possesses, specifies, or is associated with a particular level or type of resolution (such as detail, clarity, or granularity) in relation to another entity.
-
C.
enveloped
Indicates that one entity is completely or largely surrounded, covered, or enclosed by another.
-
D.
hasEnvoi
Indicates that one entity includes or is associated with an envoi, typically a concluding or dedicatory section appended to a main text or composition.
-
E.
engagementEnvelope
Indicates the spatial or contextual bounds within which an interaction, operation, or engagement between entities is valid or permitted.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 28, 2026, 11:58 a.m.