Triple
T4329234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manx law |
E96707
|
entity |
| Predicate | criminalLawInfluencedBy |
P39579
|
FINISHED |
| Object | English criminal 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: English criminal law | Statement: [Manx law, criminalLawInfluencedBy, English criminal law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: criminalLawInfluencedBy Context triple: [Manx law, criminalLawInfluencedBy, English criminal law]
-
A.
haveCriminalLaw
Indicates that an entity possesses, applies, or is governed by a system or body of criminal law.
-
B.
impactOnLaw
chosen
Indicates the effect or influence that one entity, event, or action has on laws, legal rules, or the legal system.
-
C.
crimeType
Indicates the specific category or nature of the crime associated with an event or entity.
-
D.
courtInfluence
Indicates that one party exerts or holds influence over decisions, outcomes, or behavior within a court or judicial setting.
-
E.
legalDoctrineInfluenced
Indicates that one legal doctrine has shaped, informed, or contributed to the development or interpretation of another legal doctrine.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3513545fc81909e29de7eae1829f7 |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4e13fc8190a42c519f37959d27 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:13 p.m.