Triple
T20317009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Additional State Pension |
E510404
|
entity |
| Predicate | canBeContractedOutOf |
P139635
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Additional State Pension, canBeContractedOutOf, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeContractedOutOf Context triple: [Additional State Pension, canBeContractedOutOf, yes]
-
A.
mayContractWith
Indicates that one entity is permitted or authorized to enter into a contractual agreement with another entity.
-
B.
containsContraction
Indicates that one element includes or is composed of a shortened form created by combining two words and omitting one or more letters (a contraction).
-
C.
isContractionOf
Indicates that one term is a shortened or combined form derived from another, more complete expression.
-
D.
canBeConvenedBy
Indicates that an entity (such as a group, body, or meeting) may be formally brought together or assembled by a specified agent or authority.
-
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. 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67788ca3c8190a3496fd54a5870d6 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 11:19 a.m.