Triple
T16792550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elco Brinkman |
E408146
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Brinkman |
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: Brinkman | Statement: [Elco Brinkman, familyName, Brinkman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brinkman Context triple: [Elco Brinkman, familyName, Brinkman]
-
A.
Brinkman
chosen
Brinkman is a surname of Germanic origin borne by various notable individuals across fields such as sports, politics, and the arts.
-
B.
Meco
Meco is a municipality in central Spain’s Community of Madrid, known for its location in the Henares Corridor near Alcalá de Henares.
-
C.
Nucourt
Nucourt is a small commune in the Val-d'Oise department in the Île-de-France region of northern France.
-
D.
Leumann
Leumann is a surname of likely Germanic or Swiss origin borne by individuals such as academic and public figure Christian Leumann.
-
E.
Mennekes
Mennekes is a German electrical engineering company best known in e-mobility for developing the widely adopted Type 2 AC charging connector for electric vehicles.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a7817c8190a53d0cfb5ef66a71 |
completed | April 18, 2026, 4:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00ab0e1e9c8190bb2ef0825b25f6e5 |
completed | May 10, 2026, 3:58 p.m. |
Created at: April 10, 2026, 5:22 a.m.