Triple
T10364228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morten Søborg |
E244210
|
entity |
| Predicate | hasGivenName |
P17
|
FINISHED |
| Object | Morten |
E139012
|
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: Morten | Statement: [Morten Søborg, hasGivenName, Morten]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Morten Context triple: [Morten Søborg, hasGivenName, Morten]
-
A.
Morten
chosen
Morten is a masculine given name commonly used in Scandinavian countries, derived from the Latin name Martinus.
-
B.
Magnus Manske
Magnus Manske is a German software developer and biochemist best known for creating the original version of the MediaWiki software that powers Wikipedia.
-
C.
Jørgen
Jørgen is a Scandinavian male given name, commonly used in Denmark and Norway and related to the name George.
-
D.
Johan
Johan is the given first name of J. Erik Jonsson, an American businessman and philanthropist who co-founded Texas Instruments and served as mayor of Dallas.
-
E.
Johan
Johan is the given first name of the Swedish playwright and novelist August Strindberg.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e964a53c8190b748e80850e96656 |
completed | April 7, 2026, 11:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d750c2d2748190b871b928d5a094f8 |
completed | April 9, 2026, 7:09 a.m. |
Created at: April 6, 2026, noon