Triple
T29543293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park Pobedy metro station |
E749560
|
entity |
| Predicate | isNamedAfterEvent |
P73091
|
FINISHED |
| Object | Soviet victory in the Great Patriotic War |
—
|
NE NERFINISHED |
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: Soviet victory in the Great Patriotic War | Statement: [Park Pobedy metro station, isNamedAfterEvent, Soviet victory in the Great Patriotic War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNamedAfterEvent Context triple: [Park Pobedy metro station, isNamedAfterEvent, Soviet victory in the Great Patriotic War]
-
A.
isHistoricNameOfEventAt
Indicates that a given historic name refers to or was used for a specific event that occurred at a particular place or time.
-
B.
historicallyNamedAfter
chosen
Indicates that one entity received its name from another entity at some point in the past.
-
C.
hasNamesakeNotableEvent
Indicates that one entity serves as the namesake for a notable event associated with the other entity.
-
D.
hasNamedAfterPerson
Indicates that one entity is named in honor of, or derived from the name of, a specific person.
-
E.
hasPlaceNamedAfter
Indicates that one place is named in honor of or derived from the name of another place.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 5:05 p.m.