Triple
T29035560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2203 |
E737848
|
entity |
| Predicate | supportsSSGEnvelopes |
P203937
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Yamaha YM2203, supportsSSGEnvelopes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSSGEnvelopes Context triple: [Yamaha YM2203, supportsSSGEnvelopes, yes]
-
A.
engagementEnvelope
Indicates the spatial or contextual bounds within which an interaction, operation, or engagement between entities is valid or permitted.
-
B.
hasEnvelopeShapes
Indicates that one entity possesses or is characterized by specific envelope-like shapes associated with another entity.
-
C.
supportsPackageShipments
Indicates that one entity provides the capability or service needed to handle and transport package shipments for another entity.
-
D.
supportsNonDocumentShipments
Indicates that the carrier or service is able to handle and transport shipments that consist of non-document items (e.g., goods, merchandise, or parcels).
-
E.
supportsDocumentShipments
Indicates that an entity is capable of handling or enabling the shipment of documents.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a02fb5ca96081908ff618f560011940 |
completed | May 12, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_6a02f9602b308190a97f81821e12b13f |
completed | May 12, 2026, 9:56 a.m. |
| PDg | Predicate description generation | batch_6a02fb5c09d48190a3958366560ea7f5 |
completed | May 12, 2026, 10:05 a.m. |
Created at: April 28, 2026, 9:58 a.m.