Triple
T8602849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2151 |
E203720
|
entity |
| Predicate | hasTotalOperators |
P7664
|
FINISHED |
| Object | 32 |
—
|
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: 32 | Statement: [Yamaha YM2151, hasTotalOperators, 32]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTotalOperators Context triple: [Yamaha YM2151, hasTotalOperators, 32]
-
A.
hasOperatorPerChannelCount
Indicates that each channel in a system or context is associated with a specific number of operators assigned to it.
-
B.
hasTotalNumber
chosen
Indicates that an entity is associated with a specific overall count or sum of items, elements, or units.
-
C.
numberOperational
Indicates that an entity is currently functioning and available for use in its intended operational capacity.
-
D.
hasOwnerOperator
Indicates that an entity is owned and operated by a specified party, combining both ownership and operational responsibility in a single relationship.
-
E.
typicalOperatorService
Indicates that an entity commonly performs or provides a particular operational service in a standard or expected manner.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46dc23448190a5eb63455578427e |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:24 p.m.