Triple
T2605933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Credit |
E58657
|
entity |
| Predicate | fullServiceRolloutCompleted |
P22986
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Universal Credit, fullServiceRolloutCompleted, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullServiceRolloutCompleted Context triple: [Universal Credit, fullServiceRolloutCompleted, 2018]
-
A.
fullyOperationalBy
Indicates that an entity is expected or required to be completely functional and ready for use no later than a specified time or event.
-
B.
installationCompleted
Indicates that the process of installing something has finished successfully.
-
C.
declaredFullyOperationalBy
Indicates that one entity has officially stated that another entity is completely ready and capable of functioning as intended.
-
D.
conversionCompleted
Indicates that a previously initiated conversion process has finished successfully.
-
E.
isComplete
chosen
Indicates that an action, process, or object has finished all required steps or reached its final state with nothing remaining to be done.
- 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_69ab4ac3523881909679750c9f8c2dec |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd8def9bc8190b2e013abffc7b191 |
completed | March 7, 2026, 7:50 a.m. |
| PD | Predicate disambiguation | batch_69abd80ab7248190ba06ba14fe4c5638 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:49 p.m.