Triple
T20882232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orde Wingate |
E514179
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Wingate |
—
|
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: Wingate | Statement: [Orde Wingate, familyName, Wingate]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wingate Context triple: [Orde Wingate, familyName, Wingate]
-
A.
Wingate
chosen
Wingate is a surname most notably associated with Orde Charles Wingate, an unconventional and influential British Army officer of the early 20th century.
-
B.
Wingate
Wingate is a residential and industrial suburb located within the city of Lower Hutt in the Wellington region of New Zealand.
-
C.
Bossington
Bossington is a small rural settlement in England, known for its traditional countryside character and scenic surroundings.
-
D.
Collycroft
Collycroft is a residential area and suburb within the town of Bedworth in Warwickshire, England.
-
E.
Winster
Winster is a historic village in England’s Peak District, known for its traditional stone houses, former lead-mining heritage, and well-preserved conservation 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c67a33548190b0f5ba58b001d387 |
completed | April 21, 2026, 12:36 a.m. |
Created at: April 16, 2026, 12:46 p.m.