Triple
T24570010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | convoy JW 55B |
E607907
|
entity |
| Predicate | cargoRecipient |
P52361
|
FINISHED |
| Object | Red Army |
—
|
NE NERFINISHED |
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: Red Army | Statement: [convoy JW 55B, cargoRecipient, Red Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoRecipient Context triple: [convoy JW 55B, cargoRecipient, Red Army]
-
A.
individualRecipient
Indicates that a specific individual is the direct recipient or beneficiary of something (such as an item, message, or action).
-
B.
recipientSport
Indicates that one entity is the sport associated with, received by, or designated for another entity.
-
C.
coRecipientWith
Indicates that two or more entities receive the same item, benefit, or communication together as joint recipients.
-
D.
positionOfRecipient
Indicates the spatial or contextual location associated with the recipient in a given interaction or transfer.
-
E.
recipientOf
chosen
Indicates that one entity is the receiver or beneficiary of something (such as an item, message, or action) from another entity.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a923635c819097ecac0c82ec5f29 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:28 a.m.