Triple
T19802480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiktor Kurmanowycz |
E475717
|
entity |
| Predicate | localSignificanceIn |
P89351
|
FINISHED |
| Object | Brzeżany |
—
|
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: Brzeżany | Statement: [Wiktor Kurmanowycz, localSignificanceIn, Brzeżany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localSignificanceIn Context triple: [Wiktor Kurmanowycz, localSignificanceIn, Brzeżany]
-
A.
localImportance
chosen
Indicates that something holds particular significance, influence, or priority within a specific, limited context or area rather than globally.
-
B.
cityWideSignificance
Indicates that something has importance, impact, or relevance at the scale of an entire city rather than just a local or individual level.
-
C.
localReputation
Indicates the perceived standing, trustworthiness, or esteem an entity holds within a specific local community or area.
-
D.
hasRegionalSignificance
Indicates that something holds particular importance, influence, or relevance within a specific geographic region.
-
E.
localFactorAt
Indicates a relationship where a specific factor or influence is associated with, or applies at, a particular local point, position, or 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654257cb4819096fb2aa5d1f7fbb0 |
completed | April 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.