Triple
T21485952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German destroyer Z6 Theodor Riedel |
E530116
|
entity |
| Predicate | usedInOperationType |
P1137
|
FINISHED |
| Object | 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: convoy escort | Statement: [German destroyer Z6 Theodor Riedel, usedInOperationType, convoy escort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInOperationType Context triple: [German destroyer Z6 Theodor Riedel, usedInOperationType, convoy escort]
-
A.
usedInOperation
Indicates that something (such as a tool, method, or resource) is employed or applied during the execution of a particular operation or procedure.
-
B.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
C.
usedByOperator
Indicates that something is utilized or operated by a particular operator or operating entity.
-
D.
hasOperationType
chosen
Indicates the specific kind or category of operation associated with an entity or process.
-
E.
usedInMatchType
Indicates that something (such as a rule, item, or configuration) is applied or relevant within a specific type or category of match.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea370adc8190b79fe26e2eba1dca |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:22 p.m.