Triple
T3884508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Kac |
E92905
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Kac |
E92905
|
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: Kac | Statement: [Mark Kac, familyName, Kac]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kac Context triple: [Mark Kac, familyName, Kac]
-
A.
Kac
chosen
Kac is a surname most notably associated with Polish-American mathematician Mark Kac, known for his work in probability theory and mathematical physics.
-
B.
Guralnik
Guralnik is a surname most notably associated with American theoretical physicist Gerald Guralnik, a co-discoverer of the Higgs mechanism.
-
C.
Takács
Takács is a Hungarian surname borne by numerous notable individuals across fields such as sports, music, and academia.
-
D.
Bryc
Bryc is an alternative spelling of the given name Bryce, typically used as a modern or stylistic variant.
-
E.
Kashiwara
Kashiwara is a city in Osaka Prefecture, Japan, known as a suburban residential and commercial area within the Kansai region’s rail network.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeec9029908190a7b36a3827734db1 |
completed | March 9, 2026, 3:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5125bee048190ba7553797e9fd254 |
completed | March 14, 2026, 7:46 a.m. |
Created at: March 9, 2026, 3:20 p.m.