Triple
T15124644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLA |
E361255
|
entity |
| Predicate | usedInJurisdictionType |
P105320
|
FINISHED |
| Object | provincial legislature |
—
|
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: provincial legislature | Statement: [MLA, usedInJurisdictionType, provincial legislature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInJurisdictionType Context triple: [MLA, usedInJurisdictionType, provincial legislature]
-
A.
usesJurisdictionType
chosen
Indicates that one entity applies, operates under, or is governed by a particular type or category of jurisdiction.
-
B.
hasJurisdictionalUse
Indicates that an entity has legal authority or recognized usage rights within a specific jurisdiction or territorial scope.
-
C.
usesJurisdiction
Indicates that one entity applies or operates under the legal authority or rules of a particular jurisdiction.
-
D.
existsInJurisdiction
Indicates that an entity is located within, falls under, or is subject to the authority of a particular legal or administrative jurisdiction.
-
E.
definedJurisdictionOf
Indicates that one entity formally establishes or specifies the scope, boundaries, or authority of another entity’s jurisdiction.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005a0c6888190840de4ead2306544 |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.