Triple
T27857689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Access to Justice Act 1999 |
E704131
|
entity |
| Predicate | establishedScheme |
P86592
|
FINISHED |
| Object | Community Legal Service |
—
|
NE NERFINISHED |
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: Community Legal Service | Statement: [Access to Justice Act 1999, establishedScheme, Community Legal Service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedScheme Context triple: [Access to Justice Act 1999, establishedScheme, Community Legal Service]
-
A.
designationScheme
Indicates the classification or naming system under which an entity’s designations or identifiers are defined.
-
B.
statutoryScheme
chosen
Indicates that one entity is part of, governed by, or defined within a particular statutory or legislative framework.
-
C.
schemeType
Indicates the classification or category of a scheme that an entity is associated with or operates under.
-
D.
notableScheme
Indicates that an entity is particularly recognized or prominent within a specific scheme, system, or organizational framework.
-
E.
inSchemeWith
Indicates that two entities are associated with, or categorized under, the same conceptual scheme or classification system.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 27, 2026, 6:15 p.m.