Triple
T23544138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop Jocelin of Wells |
E577840
|
entity |
| Predicate | associatedWith |
P37
|
FINISHED |
| Object | city of Wells |
—
|
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: city of Wells | Statement: [Bishop Jocelin of Wells, associatedWith, city of Wells]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: city of Wells Context triple: [Bishop Jocelin of Wells, associatedWith, city of Wells]
-
A.
city of Wells
chosen
The city of Wells is a historic cathedral city in Somerset, England, renowned for its medieval architecture and status as England’s smallest city.
-
B.
City of Wells
The City of Wells is a small historic cathedral city in Somerset, England, renowned for its medieval architecture and Wells Cathedral.
-
C.
Wells
Wells is a common English surname borne by numerous notable individuals across literature, politics, science, and the arts.
-
D.
Wells
Wells is a small city in northeastern Nevada known as a historic railroad and travel junction near the intersection of Interstate 80 and U.S. Route 93.
-
E.
Wells
Wells is a small town in southwestern Vermont known for its rural character and proximity to Lake St. Catherine.
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae1ef55c8190a93c33e704ec3b5a |
completed | April 29, 2026, 7:07 a.m. |
Created at: April 17, 2026, 6:11 p.m.