Triple
T31224794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cold War-era Royal Navy |
E796108
|
entity |
| Predicate | mainASWAreaOfOperations |
P7505
|
FINISHED |
| Object | North Atlantic Ocean |
—
|
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: North Atlantic Ocean | Statement: [Cold War-era Royal Navy, mainASWAreaOfOperations, North Atlantic Ocean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainASWAreaOfOperations Context triple: [Cold War-era Royal Navy, mainASWAreaOfOperations, North Atlantic Ocean]
-
A.
fieldOfOperation
chosen
Indicates the domain, area, or scope within which an entity operates or carries out its primary activities.
-
B.
primaryIslandOfOperation
Indicates that an entity mainly conducts its activities or operations on a specified island.
-
C.
navalOperations
Indicates involvement in planning, conducting, or supporting military activities carried out by naval forces at sea or from the sea.
-
D.
navalOperationsBy
Indicates that a set of naval operations is conducted, controlled, or carried out by a specified agent or organization.
-
E.
coordinatesMilitaryOperationsOf
Indicates having authority to plan, direct, and manage the military operations carried out by 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 9:10 p.m.