Triple
T20316393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Railways Act 2005 |
E510389
|
entity |
| Predicate | partOfLegalArea |
P2167
|
FINISHED |
| Object | UK transport 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: UK transport law | Statement: [Railways Act 2005, partOfLegalArea, UK transport law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfLegalArea Context triple: [Railways Act 2005, partOfLegalArea, UK transport law]
-
A.
legalArea
chosen
Indicates the specific field or branch of law that a legal matter, case, or document pertains to.
-
B.
hasPartInJurisidiction
Indicates that an entity includes or comprises a component, segment, or subdivision that exists or operates within a specified jurisdiction.
-
C.
regulatedArea
Indicates that an area is subject to specific rules, controls, or restrictions imposed by an authority.
-
D.
territorialJurisdictionIncludes
Indicates that one authority’s territorial jurisdiction encompasses or extends over a specified geographic area or location.
-
E.
legalLicenseJurisdiction
Indicates the legal authority or geographic area under whose laws a particular license is granted, valid, or enforced.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67787af188190bc32a3049c9c5b39 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:19 a.m.