Triple
T22470480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Obedient |
E555482
|
entity |
| Predicate | navalConvoyType |
P50418
|
FINISHED |
| Object | Arctic convoy escort |
—
|
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: Arctic convoy escort | Statement: [HMS Obedient, navalConvoyType, Arctic convoy escort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalConvoyType Context triple: [HMS Obedient, navalConvoyType, Arctic convoy escort]
-
A.
convoyType
chosen
Indicates the specific kind or classification of convoy associated with or used in the relationship between the entities.
-
B.
convoyCargo
Indicates that one entity is transporting or escorting another entity as cargo within a convoy.
-
C.
convoyProtected
Indicates that one entity provides protective escort or defense to a moving group (convoy) of other entities during transit.
-
D.
convoyComposition
Indicates that one entity is composed of, or includes as its members, the set of entities forming a convoy.
-
E.
convoyCode
Indicates that an entity is assigned or associated with a specific convoy identification code used for grouping or tracking movements.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15bdf6dfc8190aa8dc80ad92a9267 |
completed | April 29, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.