Triple
T28134876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Hayes |
E714171
|
entity |
| Predicate | hasSecurityClearance |
P20877
|
FINISHED |
| Object | access to top-secret Stargate Program information |
—
|
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: access to top-secret Stargate Program information | Statement: [Henry Hayes, hasSecurityClearance, access to top-secret Stargate Program information]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityClearance Context triple: [Henry Hayes, hasSecurityClearance, access to top-secret Stargate Program information]
-
A.
hasClearance
chosen
Indicates that one entity possesses the required authorization level or permission to access or perform actions on another entity or resource.
-
B.
hasClearanceOver
Indicates that one entity possesses authorized access rights or control privileges over another entity or resource.
-
C.
hasClearanceType
Indicates that an entity possesses a specific level or category of authorized access or security clearance.
-
D.
hasSecurityScreening
Indicates that an entity is subject to, or has undergone, a security screening process.
-
E.
hasClearanceBelow
Indicates that one entity’s clearance level is lower than another entity’s clearance level.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 27, 2026, 9:49 p.m.