Triple
T25669218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milner, Georgia |
E643612
|
entity |
| Predicate | hasProximityToRegionalCenter |
P84435
|
FINISHED |
| Object | Griffin, 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: Griffin, Georgia | Statement: [Milner, Georgia, hasProximityToRegionalCenter, Griffin, Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProximityToRegionalCenter Context triple: [Milner, Georgia, hasProximityToRegionalCenter, Griffin, Georgia]
-
A.
hasRegionalCenterNearby
chosen
Indicates that a regional center is located in close proximity to the referenced entity.
-
B.
isNearCapitalCity
Indicates that an entity is located close to, or in the immediate vicinity of, a capital city.
-
C.
featuresRegionalProximity
Indicates that one entity is located near or in close geographic proximity to a particular region or another entity.
-
D.
hasMunicipalitySeatNearby
Indicates that the municipality’s administrative seat is located in close proximity to the referenced place or entity.
-
E.
isMunicipalityNear
Indicates that one municipality is located close to another municipality or geographic reference point.
- 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 21, 2026, 7:10 p.m.