Triple
T9386941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Special Forces |
E225926
|
entity |
| Predicate | engagementCriteria |
P60049
|
FINISHED |
| Object | high-risk missions |
—
|
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: high-risk missions | Statement: [UK Special Forces, engagementCriteria, high-risk missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagementCriteria Context triple: [UK Special Forces, engagementCriteria, high-risk missions]
-
A.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
B.
engagementType
Indicates the specific kind or category of engagement or interaction that occurs between the related entities.
-
C.
engagementPolicy
chosen
Indicates the rules or guidelines that govern how parties are allowed or expected to interact or engage with each other.
-
D.
engagementRange
Indicates the distance or span within which an entity can effectively engage, interact with, or affect another entity.
-
E.
engagementTo
Indicates a formal promise or commitment between two entities to enter into a future partnership or binding relationship.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50d562a48190875d9fe3aae25a2b |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:45 p.m.