Triple
T8892264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Lambourn |
E211707
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Shaw |
E73665
|
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: Shaw | Statement: [River Lambourn, flowsThrough, Shaw]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shaw Context triple: [River Lambourn, flowsThrough, Shaw]
-
A.
Shaw
Shaw is a historic, culturally rich neighborhood in Washington, D.C., known for its African American heritage, jazz legacy, and vibrant urban revival.
-
B.
Shaw
chosen
Shaw is a town in the Metropolitan Borough of Oldham in Greater Manchester, England, known historically for its role in the textile industry.
-
C.
Shaw
Shaw is a common English and Scottish surname borne by numerous notable figures in literature, politics, and the arts.
-
D.
Shaw (partial)
Shaw is a historic Washington, D.C. neighborhood known for its African American cultural heritage, vibrant arts and nightlife, and significant role in the city’s civil rights history.
-
E.
Shaffer
Shaffer is a surname of English origin borne by various notable individuals across fields such as literature, law, and the arts.
- 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_69ca83907954819096d52a245b635841 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61ba33c48190a657fc4147a326c0 |
completed | April 1, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfabf795b08190bb4c45d6ede3b8b4 |
completed | April 3, 2026, noon |
Created at: March 30, 2026, 6:54 p.m.