Triple
T18053471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto von Below |
E431977
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | von Below |
—
|
NE NERFINISHED |
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: von Below | Statement: [Otto von Below, familyName, von Below]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: von Below Context triple: [Otto von Below, familyName, von Below]
-
A.
von Below
chosen
Von Below is a German noble family name historically associated with several notable military officers and aristocrats.
-
B.
Von
Von is the debut studio album by Icelandic post-rock band Sigur Rós, known for its atmospheric soundscapes and experimental style.
-
C.
von Cube
Von Cube is a German surname most notably borne by screenwriter Irma von Cube.
-
D.
von Daun
Von Daun is a German noble surname most notably associated with an Austrian military family prominent in the 18th century.
-
E.
von Buz
von Buz is a German noble family name historically associated with figures such as engineer and industrialist Heinrich von Buz.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4c100e7e4819084470c5b7fced334 |
completed | April 19, 2026, 11:48 a.m. |
Created at: April 10, 2026, 10:26 a.m.