Triple
T21101601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INCOSE Systems Engineering Professional certification program |
E519917
|
entity |
| Predicate | offersCredential |
P49
|
FINISHED |
| Object | INCOSE ESEP |
—
|
NE NERFINISHED |
How this triple was built (3 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: INCOSE ESEP | Statement: [INCOSE Systems Engineering Professional certification program, offersCredential, INCOSE ESEP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: INCOSE ESEP Context triple: [INCOSE Systems Engineering Professional certification program, offersCredential, INCOSE ESEP]
-
A.
INCOSE
INCOSE is a global professional organization dedicated to advancing the discipline and practice of systems engineering across industry, government, and academia.
-
B.
INCOSE competency framework
The INCOSE competency framework is a structured model that defines the knowledge, skills, and behaviors required for effective systems engineering practice and professional development.
-
C.
INCOSE Systems Engineering Professional certification program
The INCOSE Systems Engineering Professional certification program is a globally recognized credentialing scheme that validates an individual's knowledge and experience in systems engineering based on INCOSE standards and best practices.
-
D.
INCOSE Systems Engineering Vision
The INCOSE Systems Engineering Vision is a strategic document that outlines the future direction, challenges, and opportunities for the systems engineering discipline to guide practitioners, organizations, and policymakers.
-
E.
INCOSE Systems Engineering Handbook
The INCOSE Systems Engineering Handbook is a comprehensive reference guide that defines best practices, processes, and principles for the application of systems engineering across the entire system life cycle.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: INCOSE ESEP Target entity description: INCOSE ESEP is the highest-level expert certification in systems engineering awarded by the International Council on Systems Engineering to highly experienced practitioners.
-
A.
INCOSE
INCOSE is a global professional organization dedicated to advancing the discipline and practice of systems engineering across industry, government, and academia.
-
B.
INCOSE competency framework
The INCOSE competency framework is a structured model that defines the knowledge, skills, and behaviors required for effective systems engineering practice and professional development.
-
C.
INCOSE Systems Engineering Professional certification program
chosen
The INCOSE Systems Engineering Professional certification program is a globally recognized credentialing scheme that validates an individual's knowledge and experience in systems engineering based on INCOSE standards and best practices.
-
D.
INCOSE Systems Engineering Vision
The INCOSE Systems Engineering Vision is a strategic document that outlines the future direction, challenges, and opportunities for the systems engineering discipline to guide practitioners, organizations, and policymakers.
-
E.
INCOSE Systems Engineering Handbook
The INCOSE Systems Engineering Handbook is a comprehensive reference guide that defines best practices, processes, and principles for the application of systems engineering across the entire system life cycle.
- F. None of above.
Provenance (2 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_69e0b508d8dc81909be940dafe36c8f7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b5e16cc81908257ccf8c9a59117 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 2:53 p.m.