Triple
T10388563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Witten |
E244830
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Witten |
E244830
|
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: Witten | Statement: [Edward Witten, hasFamilyName, Witten]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Witten Context triple: [Edward Witten, hasFamilyName, Witten]
-
A.
Witten
chosen
Witten is a surname most notably associated with Edward Witten, a leading theoretical physicist and key figure in string theory and mathematical physics.
-
B.
Witten
Witten is a city in the Ruhr region of western Germany known for its industrial heritage and location along the Ruhr River.
-
C.
Schreiber
Schreiber is a surname most notably associated with Stuart L. Schreiber, a prominent American chemist known for his pioneering work in chemical biology and drug discovery.
-
D.
Schreiber
Schreiber is a small township and community located along the north shore of Lake Superior in northwestern Ontario, Canada.
-
E.
Wess
Wess is a given name, typically used as a shortened or variant form of Wesley.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9a59d688190b1da1ea0ed48fafa |
completed | April 7, 2026, 11:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d795b2423c8190a7c0e9b6fcbcc6db |
completed | April 9, 2026, 12:04 p.m. |
Created at: April 6, 2026, 12:05 p.m.