Triple
T9120051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Code for Crown Prosecutors |
E218822
|
entity |
| Predicate | basedOnSection |
P64960
|
FINISHED |
| Object | section 10 of the Prosecution of Offences Act 1985 |
—
|
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: section 10 of the Prosecution of Offences Act 1985 | Statement: [Code for Crown Prosecutors, basedOnSection, section 10 of the Prosecution of Offences Act 1985]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnSection Context triple: [Code for Crown Prosecutors, basedOnSection, section 10 of the Prosecution of Offences Act 1985]
-
A.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
B.
basedOnText
Indicates that something is derived, adapted, or developed from a specific text source.
-
C.
appliesToSectionOf
chosen
Indicates that something is relevant or applicable specifically to a particular section or subsection of a larger whole.
-
D.
basedOnResource
Indicates that one entity is derived from, created using, or conceptually dependent on another entity as its underlying resource.
-
E.
basedOnOutlineBy
Indicates that something (such as a work, document, or plan) is created or developed using an outline originally produced by another specified entity.
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a902e08190a7eb4728f32b9e1d |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.