Triple
T28296916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Campbeltown (I42) conversion for St Nazaire Raid |
E713594
|
entity |
| Predicate | targetedPort |
P182753
|
FINISHED |
| Object | St Nazaire |
—
|
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: St Nazaire | Statement: [HMS Campbeltown (I42) conversion for St Nazaire Raid, targetedPort, St Nazaire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetedPort Context triple: [HMS Campbeltown (I42) conversion for St Nazaire Raid, targetedPort, St Nazaire]
-
A.
controlledPort
Indicates that one entity has authority over or manages the operation or configuration of a specific port of another entity.
-
B.
registeredPort
Indicates that a specific network port number has been officially assigned and recorded for use by a particular service or protocol.
-
C.
exportPort
Indicates the port or harbor from which goods, resources, or data are sent out from one location or entity to another.
-
D.
typicalPort
Indicates that a specified port is commonly or normally used for a given service, protocol, or application.
-
E.
connectionPort
Indicates a specific port through which two components, systems, or devices are connected or can communicate.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f7908ec35881909a42f954fb9fa16e |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78fd3fd888190b7db0b563f298585 |
completed | May 3, 2026, 6:11 p.m. |
Created at: April 27, 2026, 11:32 p.m.