Triple
T32625954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sahib I Giray |
E834056
|
entity |
| Predicate | notableRaidTarget |
P205122
|
FINISHED |
| Object | Russian territories |
—
|
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: Russian territories | Statement: [Sahib I Giray, notableRaidTarget, Russian territories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRaidTarget Context triple: [Sahib I Giray, notableRaidTarget, Russian territories]
-
A.
notableBoss
Indicates that one entity is a boss or superior of another in a way that is particularly prominent, distinguished, or noteworthy.
-
B.
notableSanctuaryLocation
Indicates that a location is recognized as a significant or distinguished sanctuary site for the associated entity.
-
C.
notableHeistTarget
Indicates that an entity is a significant or high-profile target of a heist or major theft.
-
D.
notableGameLocation
Indicates that a particular place is recognized as a significant or prominent location within a game.
-
E.
notableEnclave
Indicates that one place is a distinct, noteworthy enclave located within or surrounded by another area or community.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037cab06288190b093935f235ddff2 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:06 a.m.