Triple
T3471538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perkiomen Creek |
E73270
|
entity |
| Predicate | watershedType |
P49162
|
FINISHED |
| Object | suburban |
—
|
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: suburban | Statement: [Perkiomen Creek, watershedType, suburban]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watershedType Context triple: [Perkiomen Creek, watershedType, suburban]
-
A.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
B.
basinType
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
-
C.
watershedBetween
Indicates that a geographic feature or boundary serves as the dividing line between two drainage basins or river systems.
-
D.
watershedArea
Indicates the total land area from which surface water drains into a particular water body or point in the drainage system.
-
E.
hasWatershed
Indicates that one geographic area or feature is part of, drains into, or is hydrologically defined by a particular watershed.
- F. None of above. chosen
Provenance (4 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb3af0cc81909e575828caeaeae0 |
completed | March 8, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69adae07802c8190919c49b0e65b2797 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb21a437c81908bca88d5e123d744 |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:17 p.m.