Triple
T35404701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Contractor Registration |
E1023333
|
entity |
| Predicate | verificationUsedBy |
P182935
|
FINISHED |
| Object | contracting officers |
—
|
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: contracting officers | Statement: [Central Contractor Registration, verificationUsedBy, contracting officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verificationUsedBy Context triple: [Central Contractor Registration, verificationUsedBy, contracting officers]
-
A.
verificationStatus
Indicates whether an entity, claim, or item has been checked and confirmed as authentic, accurate, or compliant according to a defined verification process.
-
B.
verificationTarget
Indicates that one entity is the object, subject, or content that another entity is intended to verify or validate.
-
C.
verificationTime
Indicates the point in time at which a verification process or check was performed or confirmed.
-
D.
identityUsedBy
Indicates that a particular identity is being employed or utilized by a specific entity.
-
E.
verificationBasis
Indicates the underlying evidence, method, or criteria used to confirm or validate that something is true, correct, or compliant.
- F. None of above. chosen
Provenance (4 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_69f7953fa72c8190bd737ef5dfa0ffc0 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 3, 2026, 4:03 p.m.