Triple
T32774528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estonia |
E838158
|
entity |
| Predicate | navalOperationsInfluencedBy |
P175106
|
FINISHED |
| Object | Gulf of Finland |
—
|
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: Gulf of Finland | Statement: [Estonia, navalOperationsInfluencedBy, Gulf of Finland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalOperationsInfluencedBy Context triple: [Estonia, navalOperationsInfluencedBy, Gulf of Finland]
-
A.
navalOperationsBy
Indicates that a set of naval operations is conducted, controlled, or carried out by a specified agent or organization.
-
B.
navalOperations
Indicates involvement in planning, conducting, or supporting military activities carried out by naval forces at sea or from the sea.
-
C.
navalTacticsImpact
Indicates how naval tactics influence the outcome, effectiveness, or dynamics of a maritime operation or engagement.
-
D.
navalDoctrineImpact
Indicates how a particular naval doctrine influences or alters the effectiveness, behavior, or outcomes of naval forces or operations.
-
E.
navalOpposition
Indicates a relationship where one party actively resists, confronts, or acts against another using naval or maritime military forces.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6ce6c76bc8190b865343d3f5810c9 |
completed | May 3, 2026, 4:26 a.m. |
Created at: May 1, 2026, 1:13 a.m.