Triple
T1966451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evarts Act |
E42697
|
entity |
| Predicate | codifiedStructureOf |
P775
|
FINISHED |
| Object | intermediate federal appellate 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: intermediate federal appellate courts | Statement: [Evarts Act, codifiedStructureOf, intermediate federal appellate courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codifiedStructureOf Context triple: [Evarts Act, codifiedStructureOf, intermediate federal appellate courts]
-
A.
codifiedIn
chosen
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
-
B.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
-
C.
programStructure
Indicates how components, modules, or elements are organized and related within a program or system.
-
D.
codificationLevel
Indicates the degree or extent to which something is formally systematized, standardized, or encoded into an explicit set of rules or structures.
-
E.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3cd47388190998b5f6800141c92 |
completed | March 7, 2026, 5:12 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.