Triple
T24967599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lordship of Clun |
E624791
|
entity |
| Predicate | appliesLegalRegime |
P12605
|
FINISHED |
| Object | Marcher law |
—
|
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: Marcher law | Statement: [Lordship of Clun, appliesLegalRegime, Marcher law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesLegalRegime Context triple: [Lordship of Clun, appliesLegalRegime, Marcher law]
-
A.
governedByLegalRegime
chosen
Indicates that an entity is subject to, regulated by, or operating under a specific legal framework or set of legal rules.
-
B.
legalCodeAppliesTo
Indicates that a particular legal code or statute is applicable to, or governs, a specified subject, situation, or entity.
-
C.
countryLegalFramework
Indicates the legal system, regulations, and institutional rules that govern actions and relationships within a given country.
-
D.
appliesLawThrough
Indicates that one entity enforces, implements, or carries out a law or legal rule by means of another entity or mechanism.
-
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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 6 a.m.