Triple
T9788120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Pinkava |
E237538
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Jan |
E103749
|
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 Pinkava, givenName, Jan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jan Context triple: [Jan Pinkava, givenName, Jan]
-
A.
Jan
chosen
Jan is the Dutch given name of Jan Peter Balkenende, the former Prime Minister of the Netherlands.
-
B.
Jan
Jan is an alternative romanization of the name Zhan, used to represent the same underlying name in different transliteration systems.
-
C.
Jan
Jan is a fictional character appearing in the Traveling Wilburys’ song “Tweeter and the Monkey Man,” which tells a noir-style crime story.
-
D.
Jan
Jan is one of the central comic characters in Alan Ayckbourn’s stage play "Bedroom Farce," involved in the interwoven marital mishaps that drive the farcical plot.
-
E.
Jan
Jan is the protagonist of the science fiction work "Red Shift," around whom the central narrative and its key events 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_69ca84da927881909bda80caecad6010 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda2131164819099e8644e40a3cab6 |
completed | April 1, 2026, 10:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1c427cb2c81909fce8e1958ab3282 |
completed | April 5, 2026, 2:08 a.m. |
Created at: March 30, 2026, 8:27 p.m.