Triple
T11931967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disability Living Allowance |
E283935
|
entity |
| Predicate | continuesFor |
P102233
|
FINISHED |
| Object | some children under 16 |
—
|
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: some children under 16 | Statement: [Disability Living Allowance, continuesFor, some children under 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuesFor Context triple: [Disability Living Allowance, continuesFor, some children under 16]
-
A.
continuesOn
Indicates that an action, process, or state persists or carries forward beyond a given point, without interruption or termination.
-
B.
continuesToward
Indicates that an entity maintains its movement or progression in the direction of a specified target or destination.
-
C.
continuedThrough
Indicates that an event, state, or process persisted without interruption across or beyond a specified point, period, or boundary.
-
D.
hasContinuation
Indicates that one entity serves as a continuation or subsequent part of another entity in a sequence or process.
-
E.
continuedBy
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by 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_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. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:45 p.m.