Triple
T4076083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FBI special agents |
E86766
|
entity |
| Predicate | requiredClearance |
P36363
|
FINISHED |
| Object | Top Secret security clearance |
—
|
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: Top Secret security clearance | Statement: [FBI special agents, requiredClearance, Top Secret security clearance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredClearance Context triple: [FBI special agents, requiredClearance, Top Secret security clearance]
-
A.
clearanceRequired
chosen
Indicates that a specific level of authorization or security clearance is needed before the related action can be performed or access can be granted.
-
B.
navigationClearanceType
Indicates the specific type or category of clearance granted for a navigation-related operation or movement.
-
C.
hasNavigationClearance
Indicates that an entity has been granted authorization to navigate through a specified area or along a particular route.
-
D.
clearanceBelow
Indicates that one entity is positioned at a lower vertical clearance level than another, typically with less space between it and an underlying reference surface.
-
E.
hasClearance
Indicates that one entity possesses the required authorization level or permission to access or perform actions on another entity or resource.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc4ba3f08190a6c6aaf6e9c99bd5 |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.