Triple

T12916993
Position Surface form Disambiguated ID Type / Status
Subject Viktor Navorski E309010 entity
Predicate reasonForStranding P107000 FINISHED
Object bureaucratic immigration limbo 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: bureaucratic immigration limbo | Statement: [Viktor Navorski, reasonForStranding, bureaucratic immigration limbo]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForStranding
Context triple: [Viktor Navorski, reasonForStranding, bureaucratic immigration limbo]
  • A. causeOfShipwreck
    Indicates the factor, event, or condition that directly led to a shipwreck occurring.
  • B. isAbandonedAtSeaBy
    Indicates that one entity is deliberately left behind or deserted at sea by another entity.
  • C. reasonForScuttling
    Indicates the specific cause or motivation that led to a vessel being deliberately scuttled.
  • D. strandedLocationType
    Indicates the type or category of place where an entity is stranded.
  • E. strandedWith
    Indicates that one entity is stuck or left without means to leave in the company or presence of another entity.
  • 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_69d7bdf92b588190acdf2a2291ac4590 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d971a1e8088190af697629baecf59f completed April 10, 2026, 9:54 p.m.
PD Predicate disambiguation batch_69d96fa9b7708190a9e9fa30f59ff580 completed April 10, 2026, 9:46 p.m.
PDg Predicate description generation batch_69d9708a86bc8190bcdcf97e845bb413 completed April 10, 2026, 9:50 p.m.
Created at: April 9, 2026, 5:41 p.m.