Triple
T32201018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | military movement route during the Battle of Gettysburg |
E822534
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | logistical route |
C30467
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: logistical route Context triple: [military movement route during the Battle of Gettysburg, instanceOf, logistical route]
-
A.
transportation route
A transportation route is a defined path or corridor used to move people or goods between locations via one or more modes of transport.
-
B.
strategic military route
chosen
A strategic military route is a planned path or corridor used to move troops, equipment, and supplies efficiently while maximizing operational advantage and minimizing vulnerability to enemy action.
-
C.
shipping route
A shipping route is a predefined path or corridor used by vessels or carriers to transport goods between specific origins and destinations, often optimized for safety, cost, and transit time.
-
D.
logistics network
A logistics network is an interconnected system of facilities, transportation modes, and information flows designed to efficiently move goods from origin to destination while optimizing cost, time, and service quality.
-
E.
riverine trade route
A riverine trade route is a navigable waterway along a river system used for the transport and exchange of goods, people, and cultural influences between settlements.
- F. None of above.
Provenance (1 batch)
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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:36 a.m.