Triple
T21632852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novak |
E533877
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Novack |
—
|
NE NERFINISHED |
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: Novack | Statement: [Novak, hasVariant, Novack]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Novack Context triple: [Novak, hasVariant, Novack]
-
A.
Vivanco
Vivanco is a Spanish-language surname of likely Iberian origin borne by various notable individuals.
-
B.
Devorski
Devorski is a surname most notably associated with Paul Devorski, a former National Hockey League referee.
-
C.
Zaslofsky
Zaslofsky is a surname most notably associated with Max Zaslofsky, an early star guard in the National Basketball Association.
-
D.
Saltykoff
Saltykoff is a variant spelling of the Russian noble family name Saltykov, historically associated with an influential aristocratic lineage in Russia.
-
E.
Kovach
chosen
Kovach is a surname of Eastern European origin, commonly found among people of Hungarian or Slavic descent and often representing an anglicized form of similar regional names.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c465ae7481908577b7209fdb2a77 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef52185dbc819096ad2fc5b7d953f8 |
completed | April 27, 2026, 12:10 p.m. |
Created at: April 16, 2026, 6:35 p.m.