Triple
T2768541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Dmitry Pozharsky |
E61395
|
entity |
| Predicate | liberationDateOfMoscow |
P14067
|
FINISHED |
| Object | 1612 |
—
|
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: 1612 | Statement: [Prince Dmitry Pozharsky, liberationDateOfMoscow, 1612]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liberationDateOfMoscow Context triple: [Prince Dmitry Pozharsky, liberationDateOfMoscow, 1612]
-
A.
liberationDate
chosen
Indicates the date on which an entity was freed, released, or liberated from a prior state of control, confinement, or oppression.
-
B.
dateOfCityCapture
Indicates the specific date on which a city was taken or captured, typically in a military or political context.
-
C.
liberationEvent
Indicates an event in which an entity is freed from control, confinement, or oppression by another entity or condition.
-
D.
liberationPlace
Indicates the place or location where an entity was liberated or set free.
-
E.
liberationAchievedBy
Indicates that a state of liberation or freedom is brought about or attained through a specific action, process, or agent.
- 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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdcfed608819080988e93df7bdf7c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.