Triple
T21805247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulloch |
E538332
|
entity |
| Predicate | hasRelatedPlaceName |
P122228
|
FINISHED |
| Object | Bulloch 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: Bulloch County, Georgia | Statement: [Bulloch, hasRelatedPlaceName, Bulloch County, Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedPlaceName Context triple: [Bulloch, hasRelatedPlaceName, Bulloch County, Georgia]
-
A.
hasPlaceNamesIn
Indicates that something contains, references, or is associated with one or more place names within it.
-
B.
hasToponymicAssociation
chosen
Indicates a relationship where one entity is associated with, derived from, or named after a particular place or geographic name (toponym).
-
C.
hasPlaceNamesakeIn
Indicates that something is named after a particular place or location.
-
D.
hasToponymicDerivatives
Indicates that a name or term serves as the source from which related place-based or toponymic names are derived.
-
E.
hasOriginToponym
Indicates that something originates from, or is derived from, the place denoted by a specific toponym (geographical name).
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07801fa8081909098d00947bf8f7f |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:53 p.m.