Triple
T36128781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yellow Belt |
E1044957
|
entity |
| Predicate | usedInMethodology |
P198714
|
FINISHED |
| Object | Six Sigma |
—
|
NE NERFINISHED |
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 | Statement: [Yellow Belt, usedInMethodology, Six Sigma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInMethodology Context triple: [Yellow Belt, usedInMethodology, Six Sigma]
-
A.
usedInPractice
Indicates that something is actually applied or implemented in real-world practice rather than just being theoretical or proposed.
-
B.
usedInMethod
Indicates that something (such as a component, variable, or resource) is utilized or referenced within the execution or implementation of a particular method.
-
C.
theoryUsed
Indicates that one entity applies, relies on, or is based upon a particular theory in its reasoning, explanation, or methodology.
-
D.
hasMethodologyFeature
Indicates that something possesses or is characterized by a particular methodological attribute, technique, or feature.
-
E.
methodologyType
Indicates the specific kind or category of method or procedure used in carrying out an activity or study.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
| PDg | Predicate description generation | batch_69feff703fec8190ab7d0633e0cc5459 |
completed | May 9, 2026, 9:33 a.m. |
Created at: May 3, 2026, 4:08 p.m.