Triple
T10606520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collegiate Circuit Courts |
E275888
|
entity |
| Predicate | proceduralNature |
P65172
|
FINISHED |
| Object | primarily appellate |
—
|
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: primarily appellate | Statement: [Collegiate Circuit Courts, proceduralNature, primarily appellate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proceduralNature Context triple: [Collegiate Circuit Courts, proceduralNature, primarily appellate]
-
A.
codeNature
Indicates that one entity characterizes or specifies the type, category, or inherent nature of another entity, often in a coded or standardized form.
-
B.
proceduralRequirement
Indicates that one entity specifies or imposes a required procedure or process that must be followed by another entity.
-
C.
hasProceduralRole
chosen
Indicates that an entity participates in a process or procedure by fulfilling a specific functional role within that process.
-
D.
naturalOrArtificial
Indicates that something is classified as either naturally occurring or artificially created.
-
E.
hasProceduralInstrument
Indicates that a procedure or process is carried out using, or with the aid of, a specified instrument or tool.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4b7aa48190bf7873b293571030 |
completed | April 8, 2026, 11:05 p.m. |
| PD | Predicate disambiguation | batch_69d6dd72c1288190adbb5e79e94c044a |
completed | April 8, 2026, 10:57 p.m. |
Created at: April 8, 2026, 7:32 p.m.