Triple
T14349760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Pacific Squadron of the Russian Baltic Fleet |
E355821
|
entity |
| Predicate | incidentWith |
P113889
|
FINISHED |
| Object | British fishing vessels |
—
|
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: British fishing vessels | Statement: [Second Pacific Squadron of the Russian Baltic Fleet, incidentWith, British fishing vessels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incidentWith Context triple: [Second Pacific Squadron of the Russian Baltic Fleet, incidentWith, British fishing vessels]
-
A.
incidentCharacterization
Indicates how an incident is classified or characterized in terms of its nature, attributes, or type.
-
B.
notableIncidentType
Indicates the specific category or kind of significant event or incident associated with an entity.
-
C.
accident
Indicates an unintended, unforeseen event or mishap occurring, often resulting in damage, injury, or disruption.
-
D.
impactEvent
Indicates that one entity physically strikes or collides with another, producing a resulting effect or change.
-
E.
investigatedEvent
Indicates that an event was the subject of an investigation or inquiry carried out by some agent.
- F. None of above. chosen
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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e8d081c8190ac805726a3e98f4c |
completed | April 14, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e8a40e4819080240c874da1842c |
completed | April 14, 2026, 12:09 p.m. |
Created at: April 10, 2026, 1:14 a.m.