Triple
T10378913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Towson |
E244580
|
entity |
| Predicate | nearbyWaterBody |
P1094
|
FINISHED |
| Object |
Herring Run
Herring Run is a small stream in the Baltimore County area of Maryland that serves as a local tributary and natural feature near Towson.
|
E952605
|
NE FINISHED |
How this triple was built (4 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: Herring Run | Statement: [Towson, nearbyWaterBody, Herring Run]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Herring Run Context triple: [Towson, nearbyWaterBody, Herring Run]
-
A.
Edwards Run
Edwards Run is a small stream in West Virginia that serves as a tributary within the Cacapon River watershed.
-
B.
Tripps Run
Tripps Run is a small stream in Northern Virginia that serves as a tributary within the local Holmes Run watershed.
-
C.
Lubbers Run
Lubbers Run is a small stream in northwestern New Jersey that feeds into the Musconetcong River and flows through a largely rural, wooded landscape.
-
D.
Kingham Run
Kingham Run is a local running event associated with the village of Kingham, typically attracting community participants for an organized road or cross-country race.
-
E.
Strouds Run
Strouds Run is a stream in southeastern Ohio whose scenic valley and surrounding woodlands form the natural centerpiece of Strouds Run State Park.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Herring Run Triple: [Towson, nearbyWaterBody, Herring Run]
Generated description
Herring Run is a small stream in the Baltimore County area of Maryland that serves as a local tributary and natural feature near Towson.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Herring Run Target entity description: Herring Run is a small stream in the Baltimore County area of Maryland that serves as a local tributary and natural feature near Towson.
-
A.
Edwards Run
Edwards Run is a small stream in West Virginia that serves as a tributary within the Cacapon River watershed.
-
B.
Tripps Run
Tripps Run is a small stream in Northern Virginia that serves as a tributary within the local Holmes Run watershed.
-
C.
Lubbers Run
Lubbers Run is a small stream in northwestern New Jersey that feeds into the Musconetcong River and flows through a largely rural, wooded landscape.
-
D.
Kingham Run
Kingham Run is a local running event associated with the village of Kingham, typically attracting community participants for an organized road or cross-country race.
-
E.
Strouds Run
Strouds Run is a stream in southeastern Ohio whose scenic valley and surrounding woodlands form the natural centerpiece of Strouds Run State Park.
- F. None of above. chosen
Provenance (5 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e98fead88190ace49f34b8a27c25 |
completed | April 7, 2026, 11:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f416ab88e48190b3089caab7987191 |
completed | May 1, 2026, 2:57 a.m. |
| NEDg | Description generation | batch_69f41f16f43c81909f5d36e8b4b0b9c3 |
completed | May 1, 2026, 3:33 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69f4225a4b5c8190958aaddbd10035b1 |
completed | May 1, 2026, 3:47 a.m. |
Created at: April 6, 2026, 12:03 p.m.