Triple
T38016913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Do Not Call Register Act 2006 |
E948521
|
entity |
| Predicate | includesExceptionFor |
P95046
|
FINISHED |
| Object | charities |
—
|
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: charities | Statement: [Do Not Call Register Act 2006, includesExceptionFor, charities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesExceptionFor Context triple: [Do Not Call Register Act 2006, includesExceptionFor, charities]
-
A.
includesException
chosen
Indicates that one entity explicitly contains, references, or accounts for a specified exception within its definition, behavior, or processing.
-
B.
isExcludedFor
Indicates that a particular entity is not allowed, applicable, or considered within a specified context, condition, or set.
-
C.
includesClasses
Indicates that one entity contains or encompasses one or more class-type entities as part of its definition or structure.
-
D.
includesClause
Indicates that one entity (typically a document, contract, or statement) contains or incorporates a specific clause as part of its content.
-
E.
includesExtension
Indicates that one entity contains or incorporates another entity as an added or supplementary extension.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.