Triple
T12814599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cranbury Historic District |
E306358
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Cranbury Brook |
E258513
|
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: Cranbury Brook | Statement: [Cranbury Historic District, contains, Cranbury Brook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cranbury Brook Context triple: [Cranbury Historic District, contains, Cranbury Brook]
-
A.
Cranbury Brook
chosen
Cranbury Brook is a small stream in central New Jersey that serves as a tributary within the Raritan River watershed.
-
B.
Foudry Brook
Foudry Brook is a small river in southern England that serves as a tributary within the River Loddon catchment.
-
C.
Werrington Brook
Werrington Brook is a small watercourse running through the Werrington area, contributing to the local drainage and natural landscape.
-
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.
Shuttleworth Brook
Shuttleworth Brook is a small watercourse in Lancashire, England, that serves as a minor tributary within the River Calder 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e9beb30819097c256a5aab9a4c8 |
completed | April 10, 2026, 9:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6af4d93508190ba63c8c54b573389 |
completed | May 3, 2026, 2:13 a.m. |
Created at: April 9, 2026, 5:31 p.m.