Triple
T5654558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Insurance record |
E124584
|
entity |
| Predicate | canShow |
P9982
|
FINISHED |
| Object | full qualifying years |
—
|
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: full qualifying years | Statement: [National Insurance record, canShow, full qualifying years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canShow Context triple: [National Insurance record, canShow, full qualifying years]
-
A.
canExhibit
chosen
Indicates that one entity has the ability or potential to display, manifest, or show a particular property, behavior, or characteristic.
-
B.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
C.
requiresShowing
Indicates that one entity must be displayed or made visible as a prerequisite or condition for another entity, action, or state.
-
D.
canAccedeTo
Indicates that one entity has the ability, permission, or right to gain access to or enter into another entity, resource, or state.
-
E.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as 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_69c0082774a481909d7e63fb2aad56ac |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022f998688190b18eb6469e8c054f |
completed | March 22, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69c01b2274b48190b2ef57ed728f785c |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:42 p.m.