Triple
T11864543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attendance Allowance |
E282247
|
entity |
| Predicate | legislationArea |
P17365
|
FINISHED |
| Object | social security law |
—
|
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: social security law | Statement: [Attendance Allowance, legislationArea, social security law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislationArea Context triple: [Attendance Allowance, legislationArea, social security law]
-
A.
areaOfLegislation
chosen
Indicates that one entity defines, concerns, or governs the legal domain or subject matter covered by another entity.
-
B.
legislatedIn
Indicates that a law, regulation, or formal rule was enacted or passed within a particular legislative body, jurisdiction, or session.
-
C.
areaOfAuthority
Indicates the domain, region, or scope within which an entity has official power, control, or responsibility.
-
D.
legalArea
Indicates the specific field or branch of law that a legal matter, case, or document pertains to.
-
E.
legislatedUnder
Indicates that a law, regulation, or policy was created, enacted, or established according to the authority, framework, or provisions of a specific higher-level law or legal regime.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a73883508190a78b5f4ba4a220df |
completed | April 10, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.