Triple
T3641620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dart Brook |
E77199
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Dart Brook |
E77199
|
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: Dart Brook | Statement: [Dart Brook, name, Dart Brook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dart Brook Context triple: [Dart Brook, name, Dart Brook]
-
A.
Dart Brook
chosen
Dart Brook is a minor river in New South Wales, Australia, that forms part of the Hunter River catchment.
-
B.
Hebble Brook
Hebble Brook is a small river in West Yorkshire, England, that flows through the town of Halifax and joins the River Calder.
-
C.
Pipp Brook
Pipp Brook is a small river in Surrey, England, that flows through the town of Dorking before joining the River Mole.
-
D.
Locke Brook
Locke Brook is a small stream in Massachusetts that serves as a tributary to the Squannacook River within the Merrimack River watershed.
-
E.
Bourn Brook
Bourn Brook is a small watercourse in Birmingham, England, that flows through urban and suburban areas before joining the River Rea.
- 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc359a91481908aef1c022f45e55c |
completed | March 8, 2026, 6:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4dafa96ac81908cda04ca12722460 |
completed | March 14, 2026, 3:50 a.m. |
Created at: March 8, 2026, 3:24 p.m.