Triple
T35406079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FedRAMP Agency ATO |
E1023365
|
entity |
| Predicate | mayLeverage |
P74042
|
FINISHED |
| Object | FedRAMP JAB Provisional ATO |
—
|
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: FedRAMP JAB Provisional ATO | Statement: [FedRAMP Agency ATO, mayLeverage, FedRAMP JAB Provisional ATO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayLeverage Context triple: [FedRAMP Agency ATO, mayLeverage, FedRAMP JAB Provisional ATO]
-
A.
mayAllowUse
Indicates that one entity has the potential or permission to allow another entity to use or access something.
-
B.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
C.
mayGrant
chosen
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
-
D.
mayTake
Indicates that an entity is permitted or allowed to take, enroll in, or participate in another entity (such as a course, resource, or opportunity).
-
E.
mayAdapt
Indicates that one entity is permitted or allowed to modify, adjust, or alter another entity.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7956353fc8190a54e35f018f4171f |
completed | May 3, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.