Triple
T23290979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stone Mills |
E590027
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Newburgh |
—
|
NE NERFINISHED |
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: Newburgh | Statement: [Stone Mills, hasSettlement, Newburgh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Newburgh Context triple: [Stone Mills, hasSettlement, Newburgh]
-
A.
Newburgh
Newburgh is a small rural village in Lancashire, England, known for its historic buildings and scenic countryside setting.
-
B.
Newburgh
Newburgh is a small historic town in eastern Scotland known for its scenic setting on the River Tay and its traditional Scottish character.
-
C.
Newburgh
Newburgh is a small historic town on the Ohio River in southwestern Indiana, known for its scenic riverfront and role as a residential community near Evansville.
-
D.
Newburgh
Newburgh is a small rural town in Penobscot County, Maine, known for its quiet residential character and proximity to the Bangor metropolitan area.
-
E.
Newburgh
chosen
Newburgh is a small rural community in eastern Ontario, Canada, known historically for its milling and agricultural roots.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e25d1af9d88190a0b9b5e8fa608618 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196cb3fec8190a95255da97dd984e |
completed | April 29, 2026, 5:27 a.m. |
Created at: April 17, 2026, 5:01 p.m.