Triple
T21539833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langwith |
E531451
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | Mansfield |
—
|
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: Mansfield | Statement: [Langwith, hasPostTown, Mansfield]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mansfield Context triple: [Langwith, hasPostTown, Mansfield]
-
A.
Mansfield
Mansfield is a historic Scottish territorial designation traditionally linked to the noble House of Murray.
-
B.
Mansfield
chosen
Mansfield is a large market town in Nottinghamshire, England, known historically for its coal mining industry and proximity to Sherwood Forest.
-
C.
Mansfield
Mansfield is a small borough in northern Pennsylvania known for its rural setting and the presence of Mansfield University of Pennsylvania.
-
D.
Mansfield
Mansfield is a surname of English origin borne by various notable individuals across politics, arts, and other fields.
-
E.
Mansfield
Mansfield is a rural town in northeastern Victoria, Australia, known as a gateway to the Victorian High Country and nearby alpine resorts.
- 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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d119e0c8190a207c0e8ae328a95 |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 16, 2026, 6:28 p.m.