Triple
T25402442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ковальский |
E636460
|
entity |
| Predicate | написание в польском |
P15778
|
FINISHED |
| Object | Kowalski |
—
|
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: Kowalski | Statement: [Ковальский, написание в польском, Kowalski]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: написание в польском Context triple: [Ковальский, написание в польском, Kowalski]
-
A.
PolishObjective
Indicates that an entity is the target or goal of a polishing action or process.
-
B.
пол
Indicates a relationship specifying an entity’s sex or gender classification.
-
C.
polishUnit
Indicates that one entity performs the action of polishing or refining another entity, typically improving its surface, appearance, or quality.
-
D.
hasNameInPolish
chosen
Indicates that an entity is associated with a specific name or label expressed in the Polish language.
-
E.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f584fbde0c8190ac451fe33848aadb |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:52 p.m.