Triple
T6900662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia Bureau of Investigation |
E159485
|
entity |
| Predicate | headquartersCounty |
P3505
|
FINISHED |
| Object | DeKalb County, Georgia |
—
|
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: DeKalb County, Georgia | Statement: [Georgia Bureau of Investigation, headquartersCounty, DeKalb County, Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headquartersCounty Context triple: [Georgia Bureau of Investigation, headquartersCounty, DeKalb County, Georgia]
-
A.
hasCountySeatOf
Indicates that a place serves as the administrative county seat (capital) of a specified county.
-
B.
headquartersMunicipality
Indicates the municipality in which an organization’s main administrative headquarters is located.
-
C.
homeCounty
chosen
Indicates that a specified county is the primary home or place of residence for a given person or entity.
-
D.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
E.
isInCountySeatOf
Indicates that one entity is located within the town or city that serves as the administrative center (county seat) of a specified county.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9603f448190bb9f963c17ca206d |
completed | March 27, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:24 p.m.