Triple
T15942386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitcliffe Common |
E386597
|
entity |
| Predicate | hasViewOf |
P854
|
FINISHED |
| Object | Ludlow town |
E82172
|
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: Ludlow town | Statement: [Whitcliffe Common, hasViewOf, Ludlow town]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ludlow town Context triple: [Whitcliffe Common, hasViewOf, Ludlow town]
-
A.
Ludlow
Ludlow is a small town in Windsor County, Vermont, best known as the home of the Okemo Mountain ski resort and a popular year-round outdoor recreation destination.
-
B.
Ludlow
Ludlow is an English-origin surname historically associated with various notable figures in politics, literature, and public life.
-
C.
Ludlow
chosen
Ludlow is a historic market town in Shropshire, England, renowned for its well-preserved medieval architecture, Norman castle, and vibrant food culture.
-
D.
Ludlow
Ludlow is a neighborhood in North Philadelphia, Pennsylvania, known for its residential character and proximity to major transit routes.
-
E.
Ludlow town centre
Ludlow town centre is the historic commercial and social heart of Ludlow, Shropshire, known for its medieval street layout, traditional markets, and well-preserved architecture.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156ce0230819089a20114a755a75a |
completed | April 16, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fffee76e9481908e74c32cb8263875 |
completed | May 10, 2026, 3:43 a.m. |
Created at: April 10, 2026, 4:53 a.m.