Triple
T31883413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagyová |
E813941
|
entity |
| Predicate | baseSurnameMeaningLanguage |
P143350
|
FINISHED |
| Object | Hungarian |
—
|
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: Hungarian | Statement: [Nagyová, baseSurnameMeaningLanguage, Hungarian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseSurnameMeaningLanguage Context triple: [Nagyová, baseSurnameMeaningLanguage, Hungarian]
-
A.
birthNameMeaning
Indicates the semantic meaning or significance associated with a person's birth name.
-
B.
languageOfNamesake
Indicates the language in which the namesake of an entity (such as a person, place, or object) is named or expressed.
-
C.
languageOfSurnameVariants
Indicates the language in which particular surname variants are used or originate.
-
D.
nameEtymologyFor
Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
-
E.
hasNameEtymologyIn
chosen
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0d99fe08190897822f9b6406e11 |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:56 p.m.