Triple
T36116488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Belt (Six Sigma) |
E1044626
|
entity |
| Predicate | typicalRoleTitle |
P38167
|
FINISHED |
| Object | Six Sigma Black Belt |
E2169913
|
NE 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: Six Sigma Black Belt | Statement: [Black Belt (Six Sigma), typicalRoleTitle, Six Sigma Black Belt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRoleTitle Context triple: [Black Belt (Six Sigma), typicalRoleTitle, Six Sigma Black Belt]
-
A.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
B.
typicalAdditionalRole
Indicates that an entity commonly or characteristically holds an extra role or function in addition to its primary one.
-
C.
titleOrRole
chosen
Indicates that one entity serves as the title, position, or role held or described by another entity.
-
D.
typicalOfficeHolderTitle
Indicates the standard or commonly used title typically held by the office holder of a given position or role.
-
E.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
- F. None of above.
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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3934020fd4819096dc08e50c2386e1 |
completed | June 22, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.