Triple
T32497954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QSA program |
E830577
|
entity |
| Predicate | qualifies |
P106510
|
FINISHED |
| Object | Qualified Security Assessors |
—
|
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: Qualified Security Assessors | Statement: [QSA program, qualifies, Qualified Security Assessors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualifies Context triple: [QSA program, qualifies, Qualified Security Assessors]
-
A.
qualifyingFor
chosen
Indicates that one entity meets the necessary conditions or criteria to be eligible for another entity, status, or action.
-
B.
qualifiesFrom
Indicates that one entity gains an official status, capability, or eligibility as a result of successfully completing or meeting the requirements of another entity.
-
C.
hasQualifying
Indicates that one entity possesses or meets a specific condition, attribute, or criterion that qualifies it in relation to another entity or context.
-
D.
hasQualification
Indicates that an entity possesses a specific qualification, credential, or competency.
-
E.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 12:59 a.m.