Triple
T14421502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Koum |
E357595
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Jan |
E866857
|
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: Jan | Statement: [Jan Koum, givenName, Jan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jan Context triple: [Jan Koum, givenName, Jan]
-
A.
Jan
Jan is the given name of the Dutch mathematician and philosopher Luitzen Egbertus Jan Brouwer, a founder of intuitionism in the foundations of mathematics.
-
B.
Jan
Jan is a common Dutch given name, often used as a masculine form of "John" and borne by many notable figures in the Netherlands and other Dutch-speaking regions.
-
C.
Jan
chosen
Jan is a common given name used in many countries, often as a variant of John or Johannes.
-
D.
Jan
Jan is a fictional young soldier and one of the core members of DC Comics' World War II-era kid commando team, the Boy Commandos.
-
E.
Jan
Jan is the main character of the work "The Misunderstanding," around whom the story’s central conflicts and themes revolve.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91102c3c81908f571a1fff3bdd47 |
completed | April 14, 2026, 7:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd5bcb131c8190935d9bacb1afc995 |
completed | May 8, 2026, 3:43 a.m. |
Created at: April 10, 2026, 1:18 a.m.