Triple
T38239973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Hush |
E1013733
|
entity |
| Predicate | intendedForces |
P116305
|
FINISHED |
| Object | Royal Navy |
—
|
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: Royal Navy | Statement: [Operation Hush, intendedForces, Royal Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedForces Context triple: [Operation Hush, intendedForces, Royal Navy]
-
A.
usesForces
Indicates that one entity applies physical, magical, or other types of forces to influence, move, or affect another entity.
-
B.
typeOfForcesDirected
Indicates that certain forces are oriented or directed toward a particular target, direction, or reference.
-
C.
targetedForce
chosen
Indicates a deliberate application of force directed at a specific target or entity.
-
D.
intendedPower
Indicates the level or amount of power that an entity is designed, planned, or expected to produce, use, or deliver under intended operating conditions.
-
E.
usedForceUnder
Indicates that one entity applied or exerted force while positioned beneath or lower than another entity.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: May 3, 2026, 4:30 p.m.