Triple
T12761535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brook Taylor |
E305006
|
entity |
| Predicate | givenName |
P17
|
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: [Brook Taylor, givenName, Brook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brook Context triple: [Brook Taylor, givenName, 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.
Johns Brook
Johns Brook is a mountain stream in the Adirondack High Peaks region of New York, popular with hikers and backpackers for its scenic cascades and access to surrounding peaks.
-
C.
Stock Brook
Stock Brook is a suburban area within the town of Chadderton in Greater Manchester, England.
-
D.
Harbor Brook
Harbor Brook is a small stream in Connecticut that feeds into the Quinnipiac River as one of its tributaries.
-
E.
Black Brook
Black Brook is a minor watercourse in northwestern England that serves as a tributary within the River Sankey catchment.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8e44188190840cd23d380bf23d |
completed | April 10, 2026, 9:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f684f298f881908ad77f2d0ab588a8 |
completed | May 2, 2026, 11:12 p.m. |
Created at: April 9, 2026, 5:28 p.m.