Triple
T14377967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnish courts |
E356522
|
entity |
| Predicate | followsLegalSystemType |
P65627
|
FINISHED |
| Object | civil law system |
—
|
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: civil law system | Statement: [Finnish courts, followsLegalSystemType, civil law system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsLegalSystemType Context triple: [Finnish courts, followsLegalSystemType, civil law system]
-
A.
hasLegalSystemType
chosen
Indicates that an entity possesses or is governed by a particular type or form of legal system.
-
B.
relatedLegalSystem
Indicates that there is an association or connection between two legal systems, such as influence, similarity, shared origin, or mutual relevance.
-
C.
countryOfLegalSystem
Indicates the relationship between a legal system and the country in which that legal system is officially established or applied.
-
D.
partOfLegalSystem
Indicates that something belongs to, is included within, or functions as a component of a particular legal system.
-
E.
separateLegalSystem
Indicates that one entity maintains its own distinct and independent legal system from another entity.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900a67e08190ab1dcf36e6bb3405 |
completed | April 14, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.