Triple
T38276778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ploshchad Muzhestva |
E1021981
|
entity |
| Predicate | cityDuringWar |
P81739
|
FINISHED |
| Object | Leningrad |
E90774
|
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: Leningrad | Statement: [Ploshchad Muzhestva, cityDuringWar, Leningrad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityDuringWar Context triple: [Ploshchad Muzhestva, cityDuringWar, Leningrad]
-
A.
stateDuringWar
Indicates that a state or condition exists specifically in the context of, or for the duration of, a war or armed conflict.
-
B.
populationDuringWar
Indicates the size or composition of a population during a specified war or wartime period.
-
C.
notableCityInConflict
chosen
Indicates that a city is prominently involved or significantly affected in a particular conflict or war.
-
D.
cityBombed
Indicates that a particular city was subjected to a bombing attack.
-
E.
alliedCities
Indicates that two cities are in an alliance or cooperative partnership with each other.
- F. None of above.
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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4193e0bb3081909eb4a8925dc47ec3 |
completed | June 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.