Triple
T35874179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltic approaches |
E1037313
|
entity |
| Predicate | securityCoordinatedBy |
P74821
|
FINISHED |
| Object | NATO naval forces |
—
|
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: NATO naval forces | Statement: [Baltic approaches, securityCoordinatedBy, NATO naval forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityCoordinatedBy Context triple: [Baltic approaches, securityCoordinatedBy, NATO naval forces]
-
A.
securityCooperationFormat
Indicates the type or structure of collaborative security arrangements or mechanisms established between entities.
-
B.
securityCooperatesWith
chosen
Indicates that one security-related entity collaborates or works jointly with another on security matters or activities.
-
C.
securityCollaboration
Indicates a cooperative relationship in which entities work together to plan, implement, or maintain security measures, policies, or defenses.
-
D.
securityCooperationFrameworkAbbreviation
Indicates that one entity is the standard abbreviated form of the name or title of a particular security cooperation framework.
-
E.
securityRepresents
Indicates that one entity serves as a representation, symbol, or embodiment of another in a security-related context (such as credentials, tokens, or certificates standing in for an identity or resource).
- 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:06 p.m.