Triple
T34931169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainian Navy gunboat Berdyansk |
E1007437
|
entity |
| Predicate | incidentDateApproximate |
P877
|
FINISHED |
| Object | November 2018 |
—
|
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: November 2018 | Statement: [Ukrainian Navy gunboat Berdyansk, incidentDateApproximate, November 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incidentDateApproximate Context triple: [Ukrainian Navy gunboat Berdyansk, incidentDateApproximate, November 2018]
-
A.
incidentTime
Indicates the specific time at which an incident or event occurs.
-
B.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
C.
attackDate
Indicates the calendar date on which an attack or assault event took place.
-
D.
injuryOccurredAt
Indicates that an injury took place at a specific location or during a particular event or time.
-
E.
approximateDateChange
Indicates that the date associated with an entity has changed in an inexact or estimated manner rather than to a precisely known new date.
- 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_69f76dc3d83881909d5c3c14455cfa2c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.