Triple
T17127667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neville Brand |
E415639
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Neville |
E486522
|
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: Neville | Statement: [Neville Brand, givenName, Neville]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Neville Context triple: [Neville Brand, givenName, Neville]
-
A.
Neville
Neville is an English surname most prominently associated with former professional footballer and coach Phil Neville.
-
B.
Neville
Neville is a fictional character appearing in the British animated children's television series "Dot."
-
C.
Neville
Neville is a small rural locality in New South Wales, Australia, situated within the Blayney Shire local government area.
-
D.
Neville
Neville is one of the central, introspective figures in Virginia Woolf’s modernist novel "The Waves," known for his poetic sensibility and intense emotional life.
-
E.
Nevil
chosen
Nevil is a given name and surname, typically considered a variant spelling of Nevill or Neville.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f027a3d081908fc1134b50db3d45 |
completed | April 18, 2026, 8:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a013a145e7481909242aab69baeb7a0 |
completed | May 11, 2026, 2:08 a.m. |
Created at: April 10, 2026, 5:36 a.m.