Triple
T12950427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inuit region of Labrador |
E309876
|
entity |
| Predicate | hasJudicialFramework |
P10526
|
FINISHED |
| Object | Canadian legal 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: Canadian legal system | Statement: [Inuit region of Labrador, hasJudicialFramework, Canadian legal system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJudicialFramework Context triple: [Inuit region of Labrador, hasJudicialFramework, Canadian legal system]
-
A.
hasJudiciary
chosen
Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
-
B.
hasJudicialPowerSource
Indicates the source or origin from which an entity derives its judicial authority or power.
-
C.
hasHumanRightsFramework
Indicates that an entity has established, adopted, or operates under a defined framework or system for recognizing, protecting, and promoting human rights.
-
D.
hasJudge
Indicates that a legal case, proceeding, or decision is presided over or decided by a particular judge.
-
E.
includesLegalFramework
Indicates that one entity encompasses, references, or incorporates a specific legal framework within its scope or content.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.