Triple
T13513662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeppe |
E322700
|
entity |
| Predicate | hasRelatedName |
P3889
|
FINISHED |
| Object | Jepser |
E322700
|
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: Jepser | Statement: [Jeppe, hasRelatedName, Jepser]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jepser Context triple: [Jeppe, hasRelatedName, Jepser]
-
A.
Jesper
Jesper is a masculine given name commonly used in Scandinavian countries and parts of Europe.
-
B.
Jeppe
chosen
Jeppe is a Scandinavian masculine given name, commonly used in Denmark and related to names like Jepser or Jepsen.
-
C.
Joppe
Joppe is a specific area or water body within the Kagerplassen lake district in the Netherlands, known for recreational boating and watersports.
-
D.
Jakan
Jakan is an alternative name for the Yakan, an indigenous ethnolinguistic group primarily inhabiting Basilan Island in the southern Philippines.
-
E.
Kasper
Kasper is a surname most notably associated with former American football wide receiver Kevin Kasper.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf87ca288190a147fbdb2f90985f |
completed | April 12, 2026, 2:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f77f8239c481909faf5a9c403b55f2 |
completed | May 3, 2026, 5:01 p.m. |
Created at: April 9, 2026, 9:44 p.m.