Triple
T36833603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hank Mobley Quintet |
E910210
|
entity |
| Predicate | featuresEnsembleSize |
P83535
|
FINISHED |
| Object | quintet |
—
|
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: quintet | Statement: [Hank Mobley Quintet, featuresEnsembleSize, quintet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresEnsembleSize Context triple: [Hank Mobley Quintet, featuresEnsembleSize, quintet]
-
A.
ensembleSize
chosen
Indicates the number of individual members or participants that make up a given group or ensemble.
-
B.
featuresEnsembleType
Indicates that one entity uses or is associated with a specific type of ensemble configuration or method in its composition or operation.
-
C.
featuresEnsembleFrom
Indicates that something includes or presents an ensemble that originates from or is derived from another source.
-
D.
intendedEnsembleSize
Indicates the number of participants or elements that a group, collection, or ensemble is designed or planned to contain.
-
E.
requiresEnsemble
Indicates that performing or realizing one entity necessitates the coordinated participation of multiple entities acting together as an ensemble.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.