Triple
T20866524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bennie Maupin |
E513776
|
entity |
| Predicate | roleInFusionEra |
P142162
|
FINISHED |
| Object | key reed player in electric jazz ensembles |
—
|
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: key reed player in electric jazz ensembles | Statement: [Bennie Maupin, roleInFusionEra, key reed player in electric jazz ensembles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFusionEra Context triple: [Bennie Maupin, roleInFusionEra, key reed player in electric jazz ensembles]
-
A.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
B.
roleInRepertoire
Indicates that an entity serves a specific role or function within a larger repertoire, collection, or set of items.
-
C.
roleInStellarFusion
Indicates the specific function or contribution an entity has within the processes that drive stellar nuclear fusion.
-
D.
roleInNebula
Indicates that an entity holds a specific function, position, or involvement within a particular nebula.
-
E.
roleInGemini10
Indicates that an entity holds a specific role or position in the context of the Gemini 10 mission or project.
- 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c460807c8190a337d8cc6c7b1438 |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:45 p.m.