Triple
T20630903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fenwick |
E506949
|
entity |
| Predicate | hasVariantSpelling |
P457
|
FINISHED |
| Object | Fenwik |
—
|
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: Fenwik | Statement: [Fenwick, hasVariantSpelling, Fenwik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fenwik Context triple: [Fenwick, hasVariantSpelling, Fenwik]
-
A.
Fenwick
chosen
Fenwick is an English surname of Anglo-Saxon origin, historically associated with families from Northumberland and surrounding regions.
-
B.
Fenwick
Fenwick is a small village and civil parish in East Ayrshire, Scotland, known for its rural character and historic roots.
-
C.
Fenwick
Fenwick is a British department store chain known for its upmarket fashion, beauty, and homeware offerings.
-
D.
Biberwier
Biberwier is a small alpine village and municipality in the Tyrolean Zugspitz Arena of western Austria, known for its mountain scenery and outdoor recreation.
-
E.
Runnemede
Runnemede is a small suburban borough in southern New Jersey, located within the Philadelphia metropolitan area.
- 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad0b0508819093c62a4ceaf860ce |
completed | April 20, 2026, 10:47 p.m. |
Created at: April 16, 2026, 11:42 a.m.