Triple
T494035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Petty Bench |
E10250
|
entity |
| Predicate | reasonToReferCases |
P14169
|
FINISHED |
| Object | cases involving constitutional questions |
—
|
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: cases involving constitutional questions | Statement: [First Petty Bench, reasonToReferCases, cases involving constitutional questions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonToReferCases Context triple: [First Petty Bench, reasonToReferCases, cases involving constitutional questions]
-
A.
selectionReason
Indicates the reason or justification for choosing or selecting one entity over alternatives.
-
B.
reasonForDecline
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
-
C.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to another entity.
-
D.
reasonForReoffer
Indicates the reason or justification for presenting something again after it was previously offered.
-
E.
reasonForElimination
Indicates the specific cause or justification for why an entity was removed, disqualified, or excluded from consideration.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f0fbfa408190aeb3b93996a35c00 |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edf90ca88190b6a182e5b6733612 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eebb2c908190960a4d0c014304cd |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.