Triple
T10825076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catoosa County |
E255476
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Ringgold Gap |
E677685
|
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: Ringgold Gap | Statement: [Catoosa County, contains, Ringgold Gap]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ringgold Gap Context triple: [Catoosa County, contains, Ringgold Gap]
-
A.
Ringgold Gap
chosen
Ringgold Gap is a strategically important mountain pass in northwestern Georgia, historically noted as the site of a significant Civil War battle.
-
B.
Hobart Gap
Hobart Gap is a strategic mountain pass in northern New Jersey that played a key role in military movements during the American Revolutionary War.
-
C.
Indian Gap
Indian Gap is a mountain pass in the Great Smoky Mountains that historically served as a key crossing point along the Tennessee–North Carolina border.
-
D.
Timber Gap
Timber Gap is a mountain pass in California’s Sierra Nevada, known as a backcountry route within Sequoia National Park.
-
E.
Snake Creek Gap
Snake Creek Gap is a strategically important mountain pass in northwestern Georgia that played a key role in Civil War military movements during the Atlanta Campaign.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d734d0389c819090a892693c4046ed |
completed | April 9, 2026, 5:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dff7c45f288190a5235b5d7000a32c |
completed | April 15, 2026, 8:40 p.m. |
Created at: April 8, 2026, 9:19 p.m.