Triple
T29372283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha DX-series synthesizer technology |
E744884
|
entity |
| Predicate | usesBuildingBlock |
P173731
|
FINISHED |
| Object | operator |
—
|
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: operator | Statement: [Yamaha DX-series synthesizer technology, usesBuildingBlock, operator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBuildingBlock Context triple: [Yamaha DX-series synthesizer technology, usesBuildingBlock, operator]
-
A.
usesBuilding
Indicates that one entity makes use of, occupies, or operates within a particular building.
-
B.
usedOnBuildingOf
Indicates that something is applied to, installed on, or otherwise utilized on the structure of a particular building.
-
C.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
D.
isBuilding
Indicates that an entity functions as or is classified as a building.
-
E.
hasBuildingFrom
Indicates a relationship where a location or site possesses or includes a building that originates from, or was constructed in, a specified time period, source, or context.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b8fe147881908ba17483c7b13f05 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 28, 2026, 2:28 p.m.