Triple
T14520445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First District Court of Appeal of Florida |
E340634
|
entity |
| Predicate | hasPanelSize |
P42161
|
FINISHED |
| Object | three-judge panels |
—
|
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: three-judge panels | Statement: [First District Court of Appeal of Florida, hasPanelSize, three-judge panels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPanelSize Context triple: [First District Court of Appeal of Florida, hasPanelSize, three-judge panels]
-
A.
hasPanel
chosen
Indicates that one entity includes, is equipped with, or is associated with a panel as a component or feature.
-
B.
hasPanelFormat
Indicates that something is associated with a particular panel layout or format used for its presentation or display.
-
C.
hasPanelComposition
Indicates that something is composed of or structured into multiple panels or panel-like sections.
-
D.
maximumPanelSize
Indicates the largest allowable or supported size for a given panel in the specified context.
-
E.
hasSize
Indicates that one entity possesses a particular physical magnitude or extent, such as length, volume, or overall dimensions.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a70b15c81908773633e989ef704 |
completed | April 14, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.