Triple
T21609224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonel Feversham |
E533254
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Feversham |
—
|
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: Feversham | Statement: [Colonel Feversham, familyName, Feversham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Feversham Context triple: [Colonel Feversham, familyName, Feversham]
-
A.
Feversham
chosen
Feversham is an English surname most notably associated with the fictional character Harry Feversham from A.E.W. Mason’s novel "The Four Feathers."
-
B.
Claverham
Claverham is a village in North Somerset, England, situated near Yatton and known for its rural character and residential community.
-
C.
Styal
Styal is a village in Cheshire, England, known for its historic cotton mill and role in the early Industrial Revolution.
-
D.
Frensham
Frensham is a rural village in Surrey, England, known for its scenic commons, ponds, and surrounding countryside.
-
E.
Windlesham
Windlesham is a village and civil parish in the Surrey Heath district of Surrey, England, known for its affluent residential character and leafy surroundings.
- 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_69e0c46411108190bba0d4176dffc9f3 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef17e7005c81908cfa86358b8dbef1 |
completed | April 27, 2026, 8:01 a.m. |
Created at: April 16, 2026, 6:33 p.m.