Triple
T8960866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Феодосій Григорович Добжанський |
E213998
|
entity |
| Predicate | етнічнеПоходження |
P194
|
FINISHED |
| Object | українець |
—
|
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: українець | Statement: [Феодосій Григорович Добжанський, етнічнеПоходження, українець]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: етнічнеПоходження Context triple: [Феодосій Григорович Добжанський, етнічнеПоходження, українець]
-
A.
ethnicOrigin
chosen
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
B.
ethnogenesisOf
Indicates the process or relationship by which a particular group, culture, or people comes into existence or forms its distinct identity.
-
C.
laterEthnicIdentity
Indicates that an entity’s ethnic identity is associated with or applies to a later period in time relative to some earlier state or context.
-
D.
sharesEthnicity
Indicates that two entities belong to the same ethnic group or share the same ethnic background.
-
E.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
- 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_69ca839cd6008190a1546a701a56710c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6748baa88190ac54e701dc4d6212 |
completed | April 1, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7 p.m.