Triple
T32359974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zalesie |
E826831
|
entity |
| Predicate | ononymType |
P95503
|
FINISHED |
| Object | choronym / oikonym (place/settlement name) |
—
|
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: choronym / oikonym (place/settlement name) | Statement: [Zalesie, ononymType, choronym / oikonym (place/settlement name)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ononymType Context triple: [Zalesie, ononymType, choronym / oikonym (place/settlement name)]
-
A.
allyType
Indicates that one entity is classified as a specific type or category of ally in relation to another entity.
-
B.
onomaType
Indicates a classification or type relationship associated with a name or designation between entities.
-
C.
nameType
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
-
D.
onomasticType
chosen
Indicates the specific kind or category of a name (e.g., personal, place, or other name type) that characterizes the naming relationship.
-
E.
InType
Indicates that an entity belongs to, is categorized under, or is an instance of a specified type or class.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be93bb548190880e9671c1dd0f29 |
completed | May 3, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:49 a.m.