Triple
T35404999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEI |
E1023341
|
entity |
| Predicate | implementedInSystem |
P22535
|
FINISHED |
| Object | SAM.gov |
—
|
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: SAM.gov | Statement: [UEI, implementedInSystem, SAM.gov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedInSystem Context triple: [UEI, implementedInSystem, SAM.gov]
-
A.
implementedOn
chosen
Indicates that something (such as a feature, standard, or specification) is realized, executed, or put into effect within or on a particular platform, system, or environment.
-
B.
isPartOfSystemWithFeature
Indicates that one entity belongs to a system that possesses a specified feature or characteristic.
-
C.
implementedInLibrary
Indicates that a particular functionality, feature, or component is realized and provided within a specific software library.
-
D.
implementedInOperation
Indicates that a particular implementation is realized, executed, or carried out within a specific operation.
-
E.
implementedFor
Indicates that one entity has been created, developed, or configured to operate on behalf of, or to fulfill the needs or requirements of, 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_69f79540f4488190957f5abf736f437f |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.