Triple
T23334250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cotter Force |
E591532
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Hawes |
—
|
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: Hawes | Statement: [Cotter Force, near, Hawes]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hawes Context triple: [Cotter Force, near, Hawes]
-
A.
Hawes
chosen
Hawes is a small market town in North Yorkshire, England, known for its scenic location in Wensleydale and its traditional cheese-making heritage.
-
B.
Hawkshaw
Hawkshaw is an English surname associated with several notable figures, including engineers, artists, and fictional detectives.
-
C.
Hawkinson
Hawkinson is a surname of likely English origin, derived as a variant of the name Hawkins.
-
D.
Hawkwell
Hawkwell is a village and civil parish in the Rochford District of Essex, England, known for its residential character and proximity to the town of Rochford.
-
E.
Hewes
Hewes is a surname most notably associated with Joseph Hewes, a signer of the United States Declaration of Independence and an early American statesman.
- 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197efd98c819083635a2b8440f3eb |
completed | April 29, 2026, 5:32 a.m. |
Created at: April 17, 2026, 5:16 p.m.