Triple
T3748548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quinnipiac River |
E81268
|
entity |
| Predicate | tributary |
P415
|
FINISHED |
| Object | Wharton Brook |
E398560
|
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: Wharton Brook | Statement: [Quinnipiac River, tributary, Wharton Brook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wharton Brook Context triple: [Quinnipiac River, tributary, Wharton Brook]
-
A.
Black Brook
Black Brook is a minor watercourse in northwestern England that serves as a tributary within the River Sankey catchment.
-
B.
Harbor Brook
chosen
Harbor Brook is a small stream in Connecticut that feeds into the Quinnipiac River as one of its tributaries.
-
C.
Grout Brook
Grout Brook is a small stream in New York that serves as one of the tributaries feeding into Skaneateles Lake in the Finger Lakes region.
-
D.
Sluice Brook
Sluice Brook is a small stream that forms part of the Mystic River watershed in Massachusetts.
-
E.
Red Brook
Red Brook is a natural watercourse and wildlife habitat in the Partington area, valued as a local site for nature and outdoor recreation.
- 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb6bf95c81909796fbc84995ae05 |
completed | March 8, 2026, 7:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b54c2971788190b8f48da3883d2ba2 |
completed | March 14, 2026, 11:53 a.m. |
Created at: March 8, 2026, 3:35 p.m.