Triple
T13375402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chattahoochee River National Recreation Area |
E319168
|
entity |
| Predicate | hasLengthAlongRiver |
P91898
|
FINISHED |
| Object | approximately 48 miles |
—
|
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: approximately 48 miles | Statement: [Chattahoochee River National Recreation Area, hasLengthAlongRiver, approximately 48 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLengthAlongRiver Context triple: [Chattahoochee River National Recreation Area, hasLengthAlongRiver, approximately 48 miles]
-
A.
hasApproxLengthAlongRiver
chosen
Indicates that an entity has an approximate measured length that follows the course of a river rather than a straight-line distance.
-
B.
hasSettlementOnRiver
Indicates that a settlement is located on or directly adjacent to a specific river.
-
C.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
D.
hasTownOnRiver
Indicates that a town is situated on or directly adjacent to a particular river.
-
E.
hasCityOnRiver
Indicates that a city is located on or along the course of a particular river.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadce3fec48190a5443d87c85477a3 |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:33 p.m.