Triple
T29116476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chickamauga Campaign |
E737057
|
entity |
| Predicate | associatedRiverOrCreek |
P86882
|
FINISHED |
| Object | Chickamauga Creek |
E421235
|
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: Chickamauga Creek | Statement: [Chickamauga Campaign, associatedRiverOrCreek, Chickamauga Creek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRiverOrCreek Context triple: [Chickamauga Campaign, associatedRiverOrCreek, Chickamauga Creek]
-
A.
isWatercourseOf
chosen
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
-
B.
associatedRiverJourney
Indicates a relationship where an entity is linked to, or involved in, a particular journey or travel event that takes place on or along a specific river.
-
C.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
-
D.
locatedOnTributaryOf
Indicates that one entity is situated along or on the banks of a tributary that flows into another specified water body.
-
E.
associatedRiverBasin
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
- F. None of above.
Provenance (4 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a030c7d03308190a102689db1e8b657 |
completed | May 12, 2026, 11:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a277befeaf08190b30dbdaa62e0ef69 |
completed | June 9, 2026, 2:35 a.m. |
| PD | Predicate disambiguation | batch_6a030a57b16c81909191270f64a77fcf |
completed | May 12, 2026, 11:09 a.m. |
Created at: April 28, 2026, 11:22 a.m.