Triple
T29101413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YMF276 |
E736647
|
entity |
| Predicate | operatorCount |
P42152
|
FINISHED |
| Object | 36 operators |
—
|
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: 36 operators | Statement: [Yamaha YMF276, operatorCount, 36 operators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorCount Context triple: [Yamaha YMF276, operatorCount, 36 operators]
-
A.
parameterCount
Indicates the number of parameters associated with a given function, method, or callable entity.
-
B.
numberOfCounts
chosen
Indicates the total quantity or tally of discrete occurrences, items, or instances associated with an entity or event.
-
C.
numberOperational
Indicates that an entity is currently functioning and available for use in its intended operational capacity.
-
D.
parameterCountRelativeTo
Indicates a relationship comparing the number of parameters of one entity (such as a function, method, or operation) to that of another entity.
-
E.
numberOfOperationalCommands
Indicates the total count of operational command units or directives associated with a given entity or context.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: April 28, 2026, 11:12 a.m.