Triple
T14889145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woolston |
E359706
|
entity |
| Predicate | hasNearbyArea |
P4647
|
FINISHED |
| Object | Weston |
E442341
|
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: Weston | Statement: [Woolston, hasNearbyArea, Weston]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Weston Context triple: [Woolston, hasNearbyArea, Weston]
-
A.
Weston
chosen
Weston is a locality within the Hunter Region of New South Wales, Australia, known historically for its coal mining and residential community.
-
B.
Weston
Weston is the reference Wayland compositor used to demonstrate and test the Wayland display server protocol.
-
C.
Weston
Weston is a suburban town in eastern Massachusetts known for its residential character, conservation land, and commuter access to Boston.
-
D.
Weston
Weston is a small rural village located within the North Hertfordshire district of England.
-
E.
Weston
Weston is a surname of English origin borne by various notable individuals across fields such as literature, business, 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded5f6cf5c8190b6b28f58fafe5d59 |
completed | April 15, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe6b61407481908a618d14c56d2abf |
completed | May 8, 2026, 11:01 p.m. |
Created at: April 10, 2026, 2:09 a.m.