Triple
T13786487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article I court |
E331270
|
entity |
| Predicate | hasJudicialPowerScope |
P111457
|
FINISHED |
| Object | limited |
—
|
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: limited | Statement: [Article I court, hasJudicialPowerScope, limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJudicialPowerScope Context triple: [Article I court, hasJudicialPowerScope, limited]
-
A.
hasJudicialPowerSource
Indicates the source or origin from which an entity derives its judicial authority or power.
-
B.
hasJurisdictionOver
Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
-
C.
hasJudiciary
Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
-
D.
hasSupervisoryJurisdictionOver
Indicates that one authority or body has the legal power to review, oversee, and, if necessary, correct or direct the actions or decisions of another authority or body.
-
E.
hasCanonicalJurisdiction
Indicates that one entity holds official, recognized authority or governing power over another entity or domain within a defined legal or organizational framework.
- F. None of above. chosen
Provenance (4 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0249e4f88190a80316394940627d |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:11 p.m.