Triple
T8556628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Davidson Niven |
E202584
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Niven |
E297279
|
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: Niven | Statement: [William Davidson Niven, familyName, Niven]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Niven Context triple: [William Davidson Niven, familyName, Niven]
-
A.
Niven
chosen
Niven is a Scottish-origin surname most famously associated with the English actor David Niven.
-
B.
Vernor
Vernor is a male given name most notably borne by the American science fiction author Vernor Vinge.
-
C.
Sagan
Sagan is a surname most famously associated with astronomer and science communicator Carl Sagan and his family.
-
D.
Sagan
Sagan is a town in present-day Żagań, Poland, historically known as a center where the astronomer Johannes Kepler conducted part of his scientific work.
-
E.
Infeld
Infeld is the surname of Leopold Infeld, a notable Polish theoretical physicist who collaborated with Albert Einstein on the theory of relativity.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe88bcce081909e12e4037a0e6323 |
completed | March 31, 2026, 3:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce893b24c0819094fead15749fe1ee |
completed | April 2, 2026, 3:20 p.m. |
Created at: March 30, 2026, 6:19 p.m.