Triple
T30028645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muskingum River Parkway |
E762950
|
entity |
| Predicate | waterwayLength |
P122474
|
FINISHED |
| Object | approximately 112 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 112 miles | Statement: [Muskingum River Parkway, waterwayLength, approximately 112 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterwayLength Context triple: [Muskingum River Parkway, waterwayLength, approximately 112 miles]
-
A.
waterwayLengthKilometres
Indicates the total length of a waterway, measured in kilometres.
-
B.
riverLength
chosen
Indicates the measured extent of a river from its source to its mouth, typically expressed as a linear distance.
-
C.
riverLengthContext
Indicates the contextual or situational information under which a river’s length is measured or considered.
-
D.
waterwayWidth
Indicates the measured width of a waterway, typically the distance across it from one bank or edge to the opposite.
-
E.
waterwaySystem
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 29, 2026, 6:49 p.m.