Triple

T31348695
Position Surface form Disambiguated ID Type / Status
Subject Zhenya Lukashin E799522 entity
Predicate transportationAccidentallyTaken P196593 FINISHED
Object flight from Moscow to Leningrad 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: flight from Moscow to Leningrad | Statement: [Zhenya Lukashin, transportationAccidentallyTaken, flight from Moscow to Leningrad]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transportationAccidentallyTaken
Context triple: [Zhenya Lukashin, transportationAccidentallyTaken, flight from Moscow to Leningrad]
  • A. lostInAccident
    Indicates that an entity was lost or destroyed as a result of an accident or unintended harmful event.
  • B. bodyTakenTo
    Indicates that a deceased person's body is transported or moved to a particular location.
  • C. notableItemLost
    Indicates that an entity has lost a particular item that is considered notable or significant.
  • D. theftStatus
    Indicates the current state or condition of an entity with respect to being stolen, such as whether it has been reported, confirmed, or suspected as theft.
  • E. wasTransportedTo
    Indicates that an entity was moved or carried from one location to another, resulting in its arrival at the specified destination.
  • F. None of above. chosen

Provenance (4 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_69f224e51614819083141459a080e97c completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fe5d58c3e48190910aa3c23485e2c4 completed May 8, 2026, 10:02 p.m.
PD Predicate disambiguation batch_69fe5c92090c8190bcfa412c0a3619df completed May 8, 2026, 9:58 p.m.
PDg Predicate description generation batch_69fe5d580d7c819097cb18d438b01d08 completed May 8, 2026, 10:02 p.m.
Created at: April 29, 2026, 9:17 p.m.