Triple
T23131311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raritan River watershed |
E577174
|
entity |
| Predicate | containsWatercourse |
P16952
|
FINISHED |
| Object | Ambrose Brook |
—
|
NE NERFINISHED |
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: Ambrose Brook | Statement: [Raritan River watershed, containsWatercourse, Ambrose Brook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ambrose Brook Context triple: [Raritan River watershed, containsWatercourse, Ambrose Brook]
-
A.
Naden Brook
Naden Brook is a small river in Greater Manchester, England, that flows through the Pennine foothills before joining the River Roch.
-
B.
Wason Brook
Wason Brook is a small stream in New Hampshire that serves as one of the tributaries feeding the Lamprey River.
-
C.
Foudry Brook
Foudry Brook is a small river in southern England that serves as a tributary within the River Loddon catchment.
-
D.
Chamberlain Brook
chosen
Chamberlain Brook is a small stream located within New Jersey’s Raritan River watershed.
-
E.
Shuttleworth Brook
Shuttleworth Brook is a small watercourse in Lancashire, England, that serves as a minor tributary within the River Calder catchment.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e87cd188190b466f7a4c9670e56 |
completed | April 29, 2026, 4:52 a.m. |
Created at: April 17, 2026, 4 p.m.