Triple
T20490078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Foxhound |
E502716
|
entity |
| Predicate | serviceEntryInHellenicNavy |
P140278
|
FINISHED |
| Object | 1944 |
—
|
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: 1944 | Statement: [HMS Foxhound, serviceEntryInHellenicNavy, 1944]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceEntryInHellenicNavy Context triple: [HMS Foxhound, serviceEntryInHellenicNavy, 1944]
-
A.
serviceEntryInOttomanNavy
Indicates that an entity served as a member of the Ottoman Navy during a specified period.
-
B.
allowedSeaService
Indicates that an entity is permitted or authorized to perform or accrue service at sea.
-
C.
vesselService
Indicates a service relationship in which one entity provides, operates, or maintains a vessel (such as a ship or boat) for another entity.
-
D.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of another entity.
-
E.
servedHarbour
Indicates that an entity provided service, support, or functions related to a harbour or port.
- 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_69e0b4b0373881909dd3e9387f82eab4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cb8e7848190a1dc497a10ae798c |
completed | April 20, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:35 a.m.