Triple
T5034121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pipp Brook |
E113378
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | Pipp Brook |
E113378
|
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: Pipp Brook | Statement: [Pipp Brook, hasName, Pipp Brook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pipp Brook Context triple: [Pipp Brook, hasName, Pipp Brook]
-
A.
Pipp Brook
chosen
Pipp Brook is a small river in Surrey, England, that flows through the town of Dorking before joining the River Mole.
-
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.
Piper Brook
Piper Brook is a small tributary stream that feeds into the Park River in Connecticut.
-
D.
Bourn Brook
Bourn Brook is a small watercourse in Birmingham, England, that flows through urban and suburban areas before joining the River Rea.
-
E.
Quorn Brook
Quorn Brook is a small watercourse in Leicestershire, England, that serves as a tributary of the River Soar.
- 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73b8646c8190b3cc20193e4639ee |
completed | March 20, 2026, 4:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be9c71b2f081908c5c4c1d9ba1ccf4 |
completed | March 21, 2026, 1:26 p.m. |
Created at: March 20, 2026, 1:36 p.m.