Triple
T34985097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Party Assessment Organizations |
E1008922
|
entity |
| Predicate | usedInProgramAbbreviation |
P63320
|
FINISHED |
| Object | FedRAMP |
—
|
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 | Statement: [Third Party Assessment Organizations, usedInProgramAbbreviation, FedRAMP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInProgramAbbreviation Context triple: [Third Party Assessment Organizations, usedInProgramAbbreviation, FedRAMP]
-
A.
isUsedInAbbreviation
Indicates that one entity functions as a shortened or abbreviated form of another entity.
-
B.
usesAbbreviationIn
chosen
Indicates that an entity is referred to by an abbreviated form within a specified context, source, or representation.
-
C.
usesAbbreviationOf
Indicates that one entity employs a shortened or abbreviated form of the name or designation of another entity.
-
D.
canBeUsedWithAbbreviation
Indicates that one entity (such as a term, phrase, or expression) is suitable to be used together with a particular abbreviation.
-
E.
usedByProgram
Indicates that a particular resource, component, or element is utilized or consumed by a specific program.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: May 3, 2026, 4:01 p.m.