Triple
T22288665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novák |
E550931
|
entity |
| Predicate | equivalentSurnameLanguage |
P116088
|
FINISHED |
| Object | Polish |
—
|
LITERAL 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: Polish | Statement: [Novák, equivalentSurnameLanguage, Polish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equivalentSurnameLanguage Context triple: [Novák, equivalentSurnameLanguage, Polish]
-
A.
equivalentSurnameInGerman
Indicates that two surnames are equivalent to each other when translated into or represented in the German language.
-
B.
isEquivalentSurnameInEnglish
Indicates that two surnames are considered equivalent when rendered or transliterated into English.
-
C.
isEquivalentSurnameInSpanish
Indicates that two surnames are considered equivalent when translated to or used in Spanish, even if their spellings or forms differ.
-
D.
equivalentGivenNameInEnglish
Indicates that two given names are equivalent in meaning or usage when expressed in English.
-
E.
languageOfSurnameVariants
chosen
Indicates the language in which particular surname variants are used or originate.
- F. None of above.
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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15609854c81908adb7681cff2c404 |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.