Triple
T25669254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Towaliga Judicial Circuit |
E643614
|
entity |
| Predicate | overseesCounty |
P163027
|
FINISHED |
| Object | Lamar County, Georgia |
E171061
|
NE 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: Lamar County, Georgia | Statement: [Towaliga Judicial Circuit, overseesCounty, Lamar County, Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseesCounty Context triple: [Towaliga Judicial Circuit, overseesCounty, Lamar County, Georgia]
-
A.
hasCountyAdministrator
Indicates that an entity is administered or overseen by a specific county administrator.
-
B.
hasCountyAdministration
Indicates that an entity is governed, managed, or served by a specific county-level administrative authority.
-
C.
inCounty
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
-
D.
overseesOffice
Indicates that one entity has managerial or supervisory responsibility for the operations or activities of a particular office.
-
E.
overseesParish
Indicates that one entity has administrative or supervisory responsibility over a parish.
- F. None of above. chosen
Provenance (5 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f63639a84c81909d700a539b458b42 |
completed | May 2, 2026, 5:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a83d36c93d48190b5a87fc851d4223e |
completed | Aug. 18, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 21, 2026, 7:11 p.m.