Triple
T2612529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinus Osendarp |
E58808
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object |
Martinus
Martinus is the given first name of Dutch sprinter and later police officer Tinus Osendarp, a notable athlete of the 1930s.
|
E281602
|
NE FINISHED |
How this triple was built (4 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: [Tinus Osendarp, givenName, Martinus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Martinus Context triple: [Tinus Osendarp, givenName, Martinus]
-
A.
Johanus
Johanus is a given name, likely a variant or diminutive of Johan, used as a personal first name in some cultures.
-
B.
Herculius
Herculius was the honorific title of the Roman emperor Maximian, associating him with the hero-god Hercules as part of Diocletian’s Tetrarchic ideology.
-
C.
Vannius
Vannius was a 1st-century AD king of the Quadi, known from Roman historical sources for his rise to power with Roman support and his later deposition in a tribal revolt.
-
D.
Armandus
Armandus is a masculine given name, a Latinized variant of Armand, historically associated with European, particularly French and Dutch, usage.
-
E.
Ahenobarbus
Ahenobarbus was the cognomen of a prominent Roman aristocratic family line to which the emperor Nero belonged.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Martinus Triple: [Tinus Osendarp, givenName, Martinus]
Generated description
Martinus is the given first name of Dutch sprinter and later police officer Tinus Osendarp, a notable athlete of the 1930s.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Martinus Target entity description: Martinus is the given first name of Dutch sprinter and later police officer Tinus Osendarp, a notable athlete of the 1930s.
-
A.
Johanus
Johanus is a given name, likely a variant or diminutive of Johan, used as a personal first name in some cultures.
-
B.
Herculius
Herculius was the honorific title of the Roman emperor Maximian, associating him with the hero-god Hercules as part of Diocletian’s Tetrarchic ideology.
-
C.
Vannius
Vannius was a 1st-century AD king of the Quadi, known from Roman historical sources for his rise to power with Roman support and his later deposition in a tribal revolt.
-
D.
Armandus
Armandus is a masculine given name, a Latinized variant of Armand, historically associated with European, particularly French and Dutch, usage.
-
E.
Ahenobarbus
Ahenobarbus was the cognomen of a prominent Roman aristocratic family line to which the emperor Nero belonged.
- F. None of above. chosen
Provenance (5 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_69ab4ac444dc819099614e534dd6021f |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd87c5fec8190a428b94b90265352 |
completed | March 7, 2026, 7:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af83e816808190aa2c91801fd3c6c7 |
completed | March 10, 2026, 2:37 a.m. |
| NEDg | Description generation | batch_69af8543a7808190968a474e64531fbd |
completed | March 10, 2026, 2:43 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69af85b60fd48190a61a3c4a73984b21 |
completed | March 10, 2026, 2:45 a.m. |
Created at: March 6, 2026, 9:50 p.m.