Triple
T5357052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nelson H. Barbour |
E102720
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Nelson |
E177649
|
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: Nelson | Statement: [Nelson H. Barbour, givenName, Nelson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nelson Context triple: [Nelson H. Barbour, givenName, Nelson]
-
A.
Nelson
chosen
Nelson is a masculine given name of English origin that has been borne by various notable figures in politics, sports, and the arts.
-
B.
Nelson
Nelson is a common English-language surname borne by numerous notable figures across politics, sports, entertainment, and academia.
-
C.
Nelson
Nelson is a former mill town in Lancashire, England, known for its industrial heritage and location near the Pennine hills.
-
D.
Nelson
Nelson is a coastal city at the top of New Zealand’s South Island, known for its arts scene, sunny climate, and access to nearby national parks.
-
E.
Jervis
Jervis is a masculine given name of English origin, historically used in various English-speaking countries.
- 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_69bd43d8f7248190b64c140734b5c9a8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd863099b081909d20f7014b98de5a |
completed | March 20, 2026, 5:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf21e6762481909278935a4eeee177 |
completed | March 21, 2026, 10:55 p.m. |
Created at: March 20, 2026, 2:01 p.m.