Triple
T9350822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kronstadt |
E225012
|
entity |
| Predicate | dateOfFinalCapture |
P30917
|
FINISHED |
| Object | 1921-03-17 |
—
|
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: 1921-03-17 | Statement: [Battle of Kronstadt, dateOfFinalCapture, 1921-03-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFinalCapture Context triple: [Battle of Kronstadt, dateOfFinalCapture, 1921-03-17]
-
A.
capturedAt
Indicates the specific time or moment at which an entity was captured, recorded, or taken.
-
B.
finalDefeatDate
chosen
Indicates the date on which an entity was ultimately and conclusively defeated.
-
C.
hasCaptureDate
Indicates the date on which something (such as an image, video, or data sample) was originally captured or recorded.
-
D.
dateOfCityCapture
Indicates the specific date on which a city was taken or captured, typically in a military or political context.
-
E.
recaptureDate
Indicates the date on which something that was previously captured or held is captured or taken back again.
- 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_69ca842abfd48190949d71c3b86eeba8 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4f9248c08190a7bb40feec2eb217 |
completed | April 1, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69cc7a68ab9481909f97cb70764697cc |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:41 p.m.