Triple
T33088722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convoy PQ 17 |
E846712
|
entity |
| Predicate | numberOfNavalEscorts |
P39920
|
FINISHED |
| Object | 6 destroyers and other escorts |
—
|
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: 6 destroyers and other escorts | Statement: [Convoy PQ 17, numberOfNavalEscorts, 6 destroyers and other escorts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfNavalEscorts Context triple: [Convoy PQ 17, numberOfNavalEscorts, 6 destroyers and other escorts]
-
A.
numberOfNaves
Indicates the specific count of naves (longitudinal sections) that a building, typically a church, possesses.
-
B.
typeOfVesselEscorted
Indicates the specific kind of vessel that is being accompanied or protected in an escorting relationship.
-
C.
numberOfShips
chosen
Indicates the quantity of ships associated with a given entity or situation.
-
D.
numberOfShipsInvolved
Indicates the total count of ships that participated or were involved in a specified event or situation.
-
E.
navalForceInvolved
Indicates that a naval military force participates in, contributes to, or is otherwise involved in a specified event or operation.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a02f441bd408190923b6b68adee8fde |
completed | May 12, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a02f3c1e64881908569423c9f298f26 |
completed | May 12, 2026, 9:32 a.m. |
Created at: May 1, 2026, 1:26 a.m.