Triple
T1914596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shenandoah River |
E38188
|
entity |
| Predicate | lengthIncludingForks |
P266
|
FINISHED |
| Object | over 150 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: over 150 miles | Statement: [Shenandoah River, lengthIncludingForks, over 150 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lengthIncludingForks Context triple: [Shenandoah River, lengthIncludingForks, over 150 miles]
-
A.
eatenWithUtensil
Indicates that something was eaten using a specific utensil as the means of consumption.
-
B.
frontLength
Indicates the length measurement of the front side or edge of an object relative to its overall dimensions.
-
C.
length
chosen
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
D.
properLengthMeasuredIn
Indicates that the proper (intrinsic or rest-frame) length of an entity is expressed using a specified unit of measurement.
-
E.
totalFiberStrands
Indicates the total number of fiber strands associated with or contained in a given entity or connection.
- 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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafeba3d88190afcce67483d8625b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.