Triple
T25074267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julijska krajina |
E628003
|
entity |
| Predicate | historicallyContested |
P168883
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Julijska krajina, historicallyContested, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyContested Context triple: [Julijska krajina, historicallyContested, true]
-
A.
historicallyContestedBy
Indicates that two or more parties have disputed or challenged control, ownership, or interpretation of something over a period of history.
-
B.
historicallyContestedSince
Indicates that a subject has been the focus of dispute, disagreement, or contention starting from a specified point in time.
-
C.
capitalContested
Indicates that the status of being the capital of a region or country is disputed or claimed by multiple parties.
-
D.
historicallyOpposedBy
Indicates that one entity has been the target of opposition, resistance, or antagonism from another entity over a historical period.
-
E.
hasHistoricalPeriodOfConflict
Indicates that there exists a specific historical period during which the related entities were engaged in conflict or hostilities.
- F. None of above. chosen
Provenance (4 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_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 18, 2026, 6:20 a.m.