Triple
T33378037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanisław Zaleski |
E854688
|
entity |
| Predicate | hasNamePartMeaningLanguage |
P195088
|
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: [Stanisław Zaleski, hasNamePartMeaningLanguage, Polish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamePartMeaningLanguage Context triple: [Stanisław Zaleski, hasNamePartMeaningLanguage, Polish]
-
A.
hasNameMeaningRelation
Indicates that there is a relationship between an entity and a name that conveys or encodes a particular meaning or significance.
-
B.
languageOfNamesake
Indicates the language in which the namesake of an entity (such as a person, place, or object) is named or expressed.
-
C.
hasLatinNameMeaning
Indicates that an entity’s Latin name conveys a specific meaning or refers to a particular concept.
-
D.
hasNameVariantLanguage
chosen
Indicates that a name variant is associated with or expressed in a specific language.
-
E.
hasEnglishNameMeaning
Indicates that an entity is associated with an English-language name along with the meaning or semantic interpretation of that name.
- 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_69f3496ca10c8190908640d18fa00832 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: May 1, 2026, 1:35 a.m.