Triple
T37902868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albanian–Yugoslav split |
E945463
|
entity |
| Predicate | positionOfAlbania |
P125561
|
FINISHED |
| Object | support for Stalin and Cominform |
—
|
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: support for Stalin and Cominform | Statement: [Albanian–Yugoslav split, positionOfAlbania, support for Stalin and Cominform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOfAlbania Context triple: [Albanian–Yugoslav split, positionOfAlbania, support for Stalin and Cominform]
-
A.
populationRankInAlbania
Indicates the relative position of an entity in terms of population size compared to other entities within Albania.
-
B.
positionOnKosovo
chosen
Indicates the stance, opinion, or policy that one entity holds regarding the political or legal status of Kosovo.
-
C.
timeZoneSideAlbania
Indicates that the referenced time zone is associated with, or applies to, the region or side of Albania.
-
D.
nearbyCityAlbania
Indicates that one city is geographically close to another city within Albania.
-
E.
lengthInAlbania
Indicates that something has a specified length measured within the context or territory of Albania.
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00037bf4148190a58593d30efdd3f8 |
completed | May 10, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_6a0000b7af608190b718fc4111bcdad8 |
completed | May 10, 2026, 3:51 a.m. |
Created at: May 3, 2026, 4:20 p.m.