Triple
T11974484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inferior Tribunals Clause |
E285003
|
entity |
| Predicate | permitsCreationOf |
P273
|
FINISHED |
| Object | lower federal courts |
—
|
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: lower federal courts | Statement: [Inferior Tribunals Clause, permitsCreationOf, lower federal courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permitsCreationOf Context triple: [Inferior Tribunals Clause, permitsCreationOf, lower federal courts]
-
A.
supportedCreationOf
Indicates that one entity actively aided, endorsed, or facilitated the bringing into existence or establishment of another entity.
-
B.
permitsExpansionOf
Indicates that one entity authorizes or enables the enlargement, extension, or increase in scope of another entity.
-
C.
mandatesCreationOf
Indicates that one entity requires or compels the establishment or creation of another entity or artifact.
-
D.
hasCreation
Indicates a relationship where one entity is the creator or originator of another entity.
-
E.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9039107e48190ae4c4efd6257dd3c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:46 p.m.