Triple
T20655133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Encounter |
E507602
|
entity |
| Predicate | serviceEndPeriod |
P84963
|
FINISHED |
| Object | 1942 |
—
|
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: 1942 | Statement: [HMS Encounter, serviceEndPeriod, 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceEndPeriod Context triple: [HMS Encounter, serviceEndPeriod, 1942]
-
A.
serviceEnded
chosen
Indicates that a previously active service or service relationship has come to an end.
-
B.
serviceEntryPeriod
Indicates the span of time during which a service is active, valid, or in effect for the related entities.
-
C.
endOfExtensionPeriod
Indicates that a previously granted extension has reached or passed its final allowable time limit.
-
D.
originalServiceEnded
Indicates that a previously existing or initial service has come to an end or has been terminated.
-
E.
statusEndsWhen
Indicates that a particular status or condition ceases to hold when a specified event, time, or state occurs.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2ec90e881909250884483429acf |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:43 a.m.