Triple
T11083126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medard Boss |
E262051
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Medard |
E404974
|
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: Medard | Statement: [Medard Boss, givenName, Medard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Medard Context triple: [Medard Boss, givenName, Medard]
-
A.
Médard
chosen
Médard is a masculine French given name of Christian origin, historically associated with Saint Médard and used in various Francophone regions.
-
B.
Mathieson
Mathieson is a surname of Scottish origin, typically regarded as a variant of Matheson and derived from a patronymic meaning “son of Matthew.”
-
C.
Bertramus
Bertramus is a Latinized variant of the given name Bertram, historically used in medieval and ecclesiastical contexts.
-
D.
Oberholtzer
Oberholtzer is a German-origin surname, often associated with Mennonite and Amish families, that serves as a variant of the Overholt family name.
-
E.
Raimondi
Raimondi is an Italian surname borne by various notable figures in fields such as science, the arts, and public life.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799bf89f48190889f08d2f5dd220a |
completed | April 9, 2026, 12:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3e79854c88190bda69cfbe4ae9d1e |
completed | April 18, 2026, 8:20 p.m. |
Created at: April 8, 2026, 9:27 p.m.