Triple
T25848877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilmington and Western Railroad |
E651145
|
entity |
| Predicate | routeFollowsWaterway |
P3624
|
FINISHED |
| Object | Red Clay Creek |
—
|
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: Red Clay Creek | Statement: [Wilmington and Western Railroad, routeFollowsWaterway, Red Clay Creek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeFollowsWaterway Context triple: [Wilmington and Western Railroad, routeFollowsWaterway, Red Clay Creek]
-
A.
isWaterway
Indicates that one entity is a water-based route or channel (such as a river, canal, or sea lane) used for travel or transport.
-
B.
navigatesWaterBody
Indicates that an entity moves through or across a body of water as a means of travel or operation.
-
C.
isInWaterwaySystem
Indicates that an entity is part of, contained within, or traverses a particular waterway network or system.
-
D.
followsWatercourse
chosen
Indicates that one entity runs alongside or traces the path of a watercourse such as a river, stream, or canal.
-
E.
hasWaterwayRole
Indicates that an entity participates in or is associated with a waterway in a specific functional capacity or role.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60239fb6881908503759ddd6b3fb1 |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 7:57 a.m.