Triple
T35599692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudo Polje |
E1028731
|
entity |
| Predicate | formerSettlementNameOf |
P86979
|
FINISHED |
| Object | Kraljevo |
—
|
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: Kraljevo | Statement: [Rudo Polje, formerSettlementNameOf, Kraljevo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerSettlementNameOf Context triple: [Rudo Polje, formerSettlementNameOf, Kraljevo]
-
A.
originalSettlementName
chosen
Indicates the name by which a settlement was originally known before any later renaming or reclassification.
-
B.
modernNameOfServedSettlement
Indicates that the object is the current, modern name of the settlement that is or was served by the subject (e.g., a facility, infrastructure, or service).
-
C.
hasFormerSettlement
Indicates that a location previously contained a settlement that no longer exists or is no longer inhabited.
-
D.
formerMunicipalityOf
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
E.
formerMainSettlement
Indicates that a location was previously the primary or most important settlement of a given area, but no longer holds that status.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0064f8efa48190956287f548a8057d |
completed | May 10, 2026, 10:59 a.m. |
| PD | Predicate disambiguation | batch_6a006471e75c8190adae99bd75e7411b |
completed | May 10, 2026, 10:56 a.m. |
Created at: May 3, 2026, 4:05 p.m.