Triple
T7892818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langho |
E183275
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Whalley |
E180670
|
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: Whalley | Statement: [Langho, locatedNear, Whalley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Whalley Context triple: [Langho, locatedNear, Whalley]
-
A.
Whalley
chosen
Whalley is a historic village in Lancashire, England, known for its medieval abbey ruins and picturesque setting in the Ribble Valley.
-
B.
Whalley
Whalley is a central urban neighbourhood in the city of Surrey, British Columbia, known for its major transit hub and ongoing high-density redevelopment.
-
C.
Aylward
Aylward is a given name notably borne by the 19th-century Irish zoologist and politician Nicholas Aylward Vigors.
-
D.
Wylie
Wylie is a suburban city in the Dallas–Fort Worth metropolitan area in northeastern Texas.
-
E.
Whiteley
Whiteley is a surname of English origin borne by various notable individuals across fields such as acting, art, and business.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a008fb88190a039fec40483ab93 |
completed | March 31, 2026, 3:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ccec781ac88190b52305beaa213415 |
completed | April 1, 2026, 9:59 a.m. |
Created at: March 30, 2026, 5 p.m.