Triple
T9831388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Much Hoole |
E238991
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Croston |
E223761
|
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: Croston | Statement: [Much Hoole, locatedNear, Croston]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Croston Context triple: [Much Hoole, locatedNear, Croston]
-
A.
Croston
chosen
Croston is a historic village in Lancashire, England, known for its picturesque rural setting, traditional architecture, and riverside location.
-
B.
Cronton
Cronton is a small village and civil parish in the Metropolitan Borough of Knowsley in Merseyside, England.
-
C.
Standerton
Standerton is a significant agricultural and commercial town situated on the banks of the Vaal River in South Africa’s Mpumalanga province.
-
D.
Shingletown
Shingletown is a small rural community in Northern California known for its forested setting near Lassen Volcanic National Park.
-
E.
Bradentown
Bradentown was the original name of the city now known as Bradenton, Florida, a Gulf Coast community in Manatee County.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3297bd88190bf8c53a4ba00e0ae |
completed | April 2, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1d5c066a08190baabf3141c10d9f3 |
completed | April 5, 2026, 3:23 a.m. |
Created at: March 30, 2026, 8:32 p.m.