Triple
T9947827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brinkman |
E195248
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Brinkmanne |
E195248
|
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: Brinkmanne | Statement: [Brinkman, hasVariant, Brinkmanne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brinkmanne Context triple: [Brinkman, hasVariant, Brinkmanne]
-
A.
Sjaalman
Sjaalman is a fictional character in Multatuli’s novel "Max Havelaar," serving as an alter ego and narrative device to expose colonial abuses in the Dutch East Indies.
-
B.
Brinkman
chosen
Brinkman is a surname of Germanic origin borne by various notable individuals across fields such as sports, politics, and the arts.
-
C.
Ockenga
Ockenga is a surname most notably associated with Harold Ockenga, a prominent American evangelical leader and theologian.
-
D.
Beerzelberg
Beerzelberg is a modest hill in Belgium known as the highest natural point in Antwerp Province.
-
E.
Bonte
Bonte is a German surname most notably borne by Friedrich Bonte, a Kriegsmarine officer during World War II.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb657b35c81909448e93999f6e77c |
completed | April 2, 2026, 12:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d23d5c6fdc81909b44d0b321201222 |
completed | April 5, 2026, 10:45 a.m. |
Created at: March 30, 2026, 8:45 p.m.