Triple
T11932049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Income Support |
E283936
|
entity |
| Predicate | requiresNationalInsuranceNumber |
P34548
|
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: [Income Support, requiresNationalInsuranceNumber, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresNationalInsuranceNumber Context triple: [Income Support, requiresNationalInsuranceNumber, yes]
-
A.
requiresTaxpayerIdentification
chosen
Indicates that providing a taxpayer identification number or equivalent tax-related identifier is necessary for the related entity, transaction, or process.
-
B.
requiresEarnedIncome
Indicates that something is conditional upon an individual or entity having earned income, such as wages or salary, in order to qualify or apply.
-
C.
nameRequirement
Indicates that there is a specified condition or constraint that a name must satisfy.
-
D.
appliesToPersonNationality
Indicates that something is relevant or applicable specifically to a person’s nationality.
-
E.
requiresCitizenship
Indicates that one entity can only obtain, access, or participate in another entity if it holds citizenship of a specified country or jurisdiction.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90305015c81908edb0d9d3d012b2e |
completed | April 10, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3af0188190bfb22be5c97b3349 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.