Triple
T10838081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgrade Offensive |
E255812
|
entity |
| Predicate | belligerent |
P375
|
FINISHED |
| Object | SS |
E1506
|
NE 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: SS | Statement: [Belgrade Offensive, belligerent, SS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SS Context triple: [Belgrade Offensive, belligerent, SS]
-
A.
SS
SS is the IATA airline designator used to identify Corsair International flights in global aviation systems.
-
B.
SS
SS is the UK postcode area covering Southend-on-Sea and surrounding parts of Essex in eastern England.
-
C.
SS
SS is the two-letter ISO 3166-1 alpha-2 country code assigned to South Sudan.
-
D.
SS
SS is a post-nominal abbreviation used by recipients of the U.S. military’s Silver Star Medal, one of the nation’s highest awards for valor in combat.
-
E.
SS
chosen
The SS was a paramilitary organization of Nazi Germany that became one of the principal instruments of terror, repression, and mass murder, including the systematic genocide of Jews and other targeted groups during World War II.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d747002b3081908726901ee83d8f38 |
completed | April 9, 2026, 6:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69deb139072081908a67e76a83575c32 |
completed | April 14, 2026, 9:27 p.m. |
Created at: April 8, 2026, 9:19 p.m.