Triple
T13660206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francis Vere |
E326974
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Vere |
E536922
|
NE FINISHED |
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: Vere | Statement: [Francis Vere, familyName, Vere]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vere Context triple: [Francis Vere, familyName, Vere]
-
A.
Vere
chosen
Vere is the given name of Vere Gordon Childe, a prominent Australian archaeologist known for his influential theories on prehistoric societies and social evolution.
-
B.
Verey
Verey is an English surname most notably associated with renowned garden designer and writer Rosemary Verey.
-
C.
Vereya
Vereya is a small historic town in Russia that was once part of the former Moscow Governorate.
-
D.
Vereker
Vereker is an Anglo-Irish noble family name historically associated with the Viscounts Gort and other members of the British and Irish aristocracy.
-
E.
Verran
Verran is a former municipality in Trøndelag county, Norway, known for its rural landscapes, forestry, and fjord-side settlements.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc61f0d808190b1cd2a6ba0d930eb |
completed | April 12, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78b08d27c8190badc612c26423c0e |
completed | May 3, 2026, 5:51 p.m. |
Created at: April 9, 2026, 9:52 p.m.