Triple
T11695748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spout Run Parkway |
E277988
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Spout Run |
E941127
|
NE 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: Spout Run | Statement: [Spout Run Parkway, namedAfter, Spout Run]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Spout Run Context triple: [Spout Run Parkway, namedAfter, Spout Run]
-
A.
Spout Run
chosen
Spout Run is a small stream in Arlington, Virginia, that flows through a wooded ravine and lends its name to the adjacent Spout Run Parkway.
-
B.
River Suck
River Suck is a major river in western Ireland that flows through counties such as Roscommon and Galway before joining the River Shannon.
-
C.
Deep Run
Deep Run is a stream in central Maryland that serves as a tributary of the Little Patuxent River within the Chesapeake Bay watershed.
-
D.
Deep Run
Deep Run is a significant tributary stream feeding into Maryland’s Patapsco River, contributing to its watershed and regional drainage system.
-
E.
The Tumbling Weir
The Tumbling Weir is an unusual circular weir and historic water feature on the River Otter in Ottery St Mary, Devon, known for its distinctive doughnut-shaped design.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47cef60819088b7cc3a3a711e4c |
completed | April 10, 2026, 7:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ef833084988190b5004c93f68dc628 |
completed | April 27, 2026, 3:39 p.m. |
Created at: April 8, 2026, 9:40 p.m.