Triple
T6984905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of Appeals of Georgia |
E161936
|
entity |
| Predicate | organizedInPanelsOf |
P40883
|
FINISHED |
| Object | 3 judges |
—
|
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: 3 judges | Statement: [Court of Appeals of Georgia, organizedInPanelsOf, 3 judges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizedInPanelsOf Context triple: [Court of Appeals of Georgia, organizedInPanelsOf, 3 judges]
-
A.
hasPanel
Indicates that one entity includes, is equipped with, or is associated with a panel as a component or feature.
-
B.
panelDivision
Indicates a relationship where a larger panel or board is divided into smaller sections or segments.
-
C.
centralPanelDepicts
Indicates that the central panel of a multi-part work (such as a triptych or polyptych) visually represents or portrays a particular subject or scene.
-
D.
numberOfPanels
chosen
Indicates the total count of distinct panels associated with or contained within a given entity.
-
E.
organizedAs
Indicates how elements are structured, arranged, or grouped according to a particular organizing principle or scheme.
- 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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbbd926c8190a8b60527bd553fa3 |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:31 p.m.