Triple
T9232891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooks |
E221862
|
entity |
| Predicate | derivedFrom |
P909
|
FINISHED |
| Object | Brook |
E651058
|
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: Brook | Statement: [Brooks, derivedFrom, Brook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brook Context triple: [Brooks, derivedFrom, Brook]
-
A.
Brook
chosen
Brook is a given name used for both males and females, often associated with the natural imagery of a small stream.
-
B.
Stock Brook
Stock Brook is a suburban area within the town of Chadderton in Greater Manchester, England.
-
C.
Harbor Brook
Harbor Brook is a small stream in Connecticut that feeds into the Quinnipiac River as one of its tributaries.
-
D.
Black Brook
Black Brook is a minor watercourse in northwestern England that serves as a tributary within the River Sankey catchment.
-
E.
Lenox Brook
Lenox Brook is a smaller watercourse or tributary that forms part of the Park River system.
- 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccee1a7e9881908e0c11f242162017 |
completed | April 1, 2026, 10:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d09bb6b6f08190ab062265b0adacf9 |
completed | April 4, 2026, 5:03 a.m. |
Created at: March 30, 2026, 7:29 p.m.