Triple
T24938031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawaii Circuit Court |
E623370
|
entity |
| Predicate | secondCircuitCovers |
P163817
|
FINISHED |
| Object | County of Maui |
—
|
NE NERFINISHED |
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: County of Maui | Statement: [Hawaii Circuit Court, secondCircuitCovers, County of Maui]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondCircuitCovers Context triple: [Hawaii Circuit Court, secondCircuitCovers, County of Maui]
-
A.
secondaryCircuit
Indicates that one entity functions as the secondary electrical circuit associated with, or derived from, another primary circuit.
-
B.
secondCircuitHolding
Indicates a legal holding or decision issued by the United States Court of Appeals for the Second Circuit.
-
C.
thirdCircuitCovers
Indicates that a legal case or matter falls under the jurisdiction or authority of the United States Court of Appeals for the Third Circuit.
-
D.
eachCircuitCovers
Indicates that every circuit in a given set or system includes or spans all required elements, areas, or components it is intended to cover.
-
E.
secondSeries
Indicates that one entity is the second installment or season in a series relative to another entity.
- 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 18, 2026, 5:30 a.m.