Triple
T621038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Court of Appeals for the Eighth Circuit |
E14512
|
entity |
| Predicate | authorizedJudges |
P16419
|
FINISHED |
| Object | 11 |
—
|
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: 11 | Statement: [United States Court of Appeals for the Eighth Circuit, authorizedJudges, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorizedJudges Context triple: [United States Court of Appeals for the Eighth Circuit, authorizedJudges, 11]
-
A.
authorizedJudgeships
chosen
Indicates the number or set of judicial positions that are officially established and permitted by law or authority for a given court or jurisdiction.
-
B.
numberOfJudges
Indicates the total count of judges associated with a particular case, event, or entity.
-
C.
judgesTerm
Indicates that one entity formally evaluates or makes a judgment about a specific term or expression.
-
D.
styleOfJudges
Indicates the characteristic manner or approach that judges use when performing their judging role.
-
E.
judgeAppointmentBy
Indicates that one entity is appointed to the role of judging or evaluating another entity by a specific authority or process.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e3e5d80819096e72e11b533f931 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfe9bc081909a01b4b3b48f03b7 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.