Triple
T18278080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crassier |
E437790
|
entity |
| Predicate | hasLocalLawSystem |
P6190
|
FINISHED |
| Object | Swiss 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: Swiss law | Statement: [Crassier, hasLocalLawSystem, Swiss law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalLawSystem Context triple: [Crassier, hasLocalLawSystem, Swiss law]
-
A.
appliesLocalLaw
Indicates that a legal rule, decision, or authority is governed by and enforced under the laws of a specific local jurisdiction.
-
B.
hasExtendedLawSystem
Indicates that an entity possesses a comprehensive, detailed, and well-developed system of laws or legal regulations.
-
C.
legalSystemRegion
Indicates the geographic or jurisdictional region within which a particular legal system is applicable or in force.
-
D.
legalJurisdiction
chosen
Indicates the legal authority or geographic area whose laws and courts have the power to govern, regulate, or adjudicate matters involving the related entities.
-
E.
countryOfLegalSystem
Indicates the relationship between a legal system and the country in which that legal system is officially established or applied.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50053cc808190b46a3ec9d96936fe |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.