Triple
T1316347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Georgia |
E28112
|
entity |
| Predicate | roughlyAround |
P17801
|
FINISHED |
| Object | geographic center of Georgia (U.S. state) |
—
|
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: geographic center of Georgia (U.S. state) | Statement: [Central Georgia, roughlyAround, geographic center of Georgia (U.S. state)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roughlyAround Context triple: [Central Georgia, roughlyAround, geographic center of Georgia (U.S. state)]
-
A.
around
chosen
Indicates that one entity is located or moves on all or most sides of another entity, encircling or surrounding it spatially.
-
B.
round
Indicates that an entity has a circular or approximately circular shape or form.
-
C.
createdAround
Indicates that something was brought into existence or produced approximately at a particular time or within an imprecise time period.
-
D.
emergedAround
Indicates that something came into existence or became noticeable at approximately a particular time or period.
-
E.
approximateRadius
Indicates that one entity specifies or provides an estimated value for the radius of another entity.
- 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c175079481909077cf11ed72d6fa |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beebcb348190964bd7215811942c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.