Triple
T33154691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augusta, Kentucky |
E848536
|
entity |
| Predicate | Augusta Ferry crosses |
P152288
|
FINISHED |
| Object | Ohio River |
—
|
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: Ohio River | Statement: [Augusta, Kentucky, Augusta Ferry crosses, Ohio River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Augusta Ferry crosses Context triple: [Augusta, Kentucky, Augusta Ferry crosses, Ohio River]
-
A.
bodyOfWaterCrossedByFerry
chosen
Indicates that a body of water is traversed or crossed by a ferry service.
-
B.
hasFerryService
Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
-
C.
hasFerryComponent
Indicates that something includes or is associated with a ferry-related part, feature, or segment within its structure or operation.
-
D.
wasMainRiverCrossingFor
Indicates that one river crossing (such as a bridge, ford, or ferry) served as the primary or most significant crossing point for a particular route, area, or settlement.
-
E.
hasFerryType
Indicates that an entity (such as a ferry route or service) is associated with a specific type or category of ferry.
- 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_69f3495b02d08190bb3d366823dffc21 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:28 a.m.