Triple
T35404692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Contractor Registration |
E1023333
|
entity |
| Predicate | requiredRegistrationFrequency |
P8512
|
FINISHED |
| Object | annual renewal |
—
|
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: annual renewal | Statement: [Central Contractor Registration, requiredRegistrationFrequency, annual renewal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredRegistrationFrequency Context triple: [Central Contractor Registration, requiredRegistrationFrequency, annual renewal]
-
A.
requiresRegistrationFor
Indicates that one entity can only access, use, or participate in another entity if a prior registration process has been completed.
-
B.
recommendedUsageFrequency
Indicates how often something is advised or prescribed to be used within a given time period.
-
C.
frequencyRequirement
chosen
Indicates a constraint specifying how often an action, event, or condition must occur within a given context or time frame.
-
D.
serviceFrequencyType
Indicates how often a service occurs or is scheduled within a given time period.
-
E.
registrationRequirement
Indicates that an entity is obligated to formally register with a specified authority, system, or registry under certain conditions.
- 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_69ffa15d53208190ab8574d6c7913e18 |
completed | May 9, 2026, 9:04 p.m. |
| PD | Predicate disambiguation | batch_69ff9eee681c81909434e79c627cb528 |
completed | May 9, 2026, 8:54 p.m. |
Created at: May 3, 2026, 4:03 p.m.