Triple
T13112849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chickahominy River |
E311013
|
entity |
| Predicate | hasBasinNamed |
P108105
|
FINISHED |
| Object | Chickahominy River watershed |
—
|
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: Chickahominy River watershed | Statement: [Chickahominy River, hasBasinNamed, Chickahominy River watershed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBasinNamed Context triple: [Chickahominy River, hasBasinNamed, Chickahominy River watershed]
-
A.
hasBasinFunction
Indicates that something serves the role or performs the function of a basin, such as collecting, holding, or draining water or other substances.
-
B.
hasSettlementInBasin
Indicates that a settlement is located within the geographic area of a specific basin.
-
C.
locatedInBasin
Indicates that one geographical or hydrological feature lies within the drainage or catchment area of a specified basin.
-
D.
formsBasinWith
Indicates that one geographic feature combines with another to create or define a shared basin or catchment area.
-
E.
basin
Indicates a geographic area where surface water drains into a common outlet, such as a river, lake, or ocean.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9817f8ee8819084078b4bec5e4f18 |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98134df64819084a5674f9475dcc2 |
completed | April 10, 2026, 11:01 p.m. |
Created at: April 9, 2026, 9:05 p.m.