Triple
T26408545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIST |
E663895
|
entity |
| Predicate | roleInAES |
P184835
|
FINISHED |
| Object | organized public evaluation of candidate algorithms |
—
|
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: organized public evaluation of candidate algorithms | Statement: [NIST, roleInAES, organized public evaluation of candidate algorithms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInAES Context triple: [NIST, roleInAES, organized public evaluation of candidate algorithms]
-
A.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
B.
roleInWPA3
Indicates that an entity holds a specific role or function within the WPA3 (Wi‑Fi Protected Access 3) security protocol or framework.
-
C.
roleInICE
Indicates that an entity holds a specific role or function within an ICE (Immigration and Customs Enforcement) context or organization.
-
D.
roleInAssembly
Indicates the specific function, position, or responsibility an entity holds within a particular assembly or gathering.
-
E.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: April 26, 2026, 11:36 p.m.