Triple
T20231417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piekarski |
E495534
|
entity |
| Predicate | derivedFromPolishWord |
P12512
|
FINISHED |
| Object | piekarz |
—
|
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: piekarz | Statement: [Piekarski, derivedFromPolishWord, piekarz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivedFromPolishWord Context triple: [Piekarski, derivedFromPolishWord, piekarz]
-
A.
derivedFrom
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
B.
hasNameInPolish
Indicates that an entity is associated with a specific name or label expressed in the Polish language.
-
C.
derivedFromLexeme
Indicates that one linguistic form or expression originates from, or is morphologically or semantically based on, a particular lexeme.
-
D.
etymologicalForm
chosen
Indicates that one linguistic form is derived from, or historically originates in, another form as its etymological source.
-
E.
officialNamePolish
Indicates the official or legally recognized name of an entity as expressed in the Polish language.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fddafac819089cef4158f5e0ab5 |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.