Triple
T11839266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martinus Osendarp |
E281602
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Martinus |
E281602
|
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: Martinus | Statement: [Martinus Osendarp, givenName, Martinus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Martinus Context triple: [Martinus Osendarp, givenName, Martinus]
-
A.
Martinus
chosen
Martinus is the given first name of Dutch sprinter and later police officer Tinus Osendarp, a notable athlete of the 1930s.
-
B.
Thurinus
Thurinus was an early cognomen of the Roman statesman Gaius Octavius, who later became the first Roman emperor Augustus.
-
C.
Emericus
Emericus is the Latin form of the Hungarian given name Imre, historically used in ecclesiastical and scholarly contexts.
-
D.
Togodumnus
Togodumnus was a 1st-century AD British tribal leader, likely a king of the Catuvellauni, who opposed the Roman invasion of Britain under Emperor Claudius.
-
E.
Johanus
Johanus is a given name, likely a variant or diminutive of Johan, used as a personal first name in some cultures.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a63106b48190917817ec40d21a49 |
completed | April 10, 2026, 7:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f167766c048190b8aaf09732d338d8 |
completed | April 29, 2026, 2:05 a.m. |
Created at: April 8, 2026, 9:43 p.m.