Triple
T25074284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julijska krajina |
E628003
|
entity |
| Predicate | wasDividedBetween |
P157617
|
FINISHED |
| Object | Socialist Republic of Slovenia |
—
|
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: Socialist Republic of Slovenia | Statement: [Julijska krajina, wasDividedBetween, Socialist Republic of Slovenia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasDividedBetween Context triple: [Julijska krajina, wasDividedBetween, Socialist Republic of Slovenia]
-
A.
wasDividedBetween
chosen
Indicates that something was partitioned into portions that were allocated to two or more distinct recipients or groups.
-
B.
wasDividedFrom
Indicates that one entity was separated or split off from another entity, resulting in two distinct parts or groups.
-
C.
wasDividedByTreaty
Indicates that an entity (such as a territory or region) was partitioned or separated as the result of a formal treaty or agreement.
-
D.
historicallyDividedInto
Indicates that an entity was separated into multiple distinct parts or regions during a past historical period.
-
E.
wasDividedFromYear
Indicates that an entity began to be separated or partitioned starting from a specified year.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f45d177c3881909ac5058e3e866d93 |
completed | May 1, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:20 a.m.