Triple
T29181990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2149 |
E739767
|
entity |
| Predicate | hasEnvelopeShapes |
P180521
|
FINISHED |
| Object | multiple |
—
|
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: multiple | Statement: [Yamaha YM2149, hasEnvelopeShapes, multiple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnvelopeShapes Context triple: [Yamaha YM2149, hasEnvelopeShapes, multiple]
-
A.
envelopeShapes
Indicates a relationship where one entity defines or determines the geometric or boundary shape(s) that enclose or outline another entity.
-
B.
hasBillShape
Indicates that one entity has a bill whose shape matches the specified form or category.
-
C.
enveloped
Indicates that one entity is completely or largely surrounded, covered, or enclosed by another.
-
D.
hasArchShape
Indicates that something possesses or exhibits an arched or curved shape.
-
E.
hasBayShape
Indicates that an entity possesses or exhibits a particular geometric or physical shape characteristic of a bay.
- F. None of above. chosen
Provenance (4 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_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 28, 2026, 11:58 a.m.