Triple

T21577240
Position Surface form Disambiguated ID Type / Status
Subject Der Alte E532427 entity
Predicate rankInFiction P121402 FINISHED
Object Kapitänleutnant 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: Kapitänleutnant | Statement: [Der Alte, rankInFiction, Kapitänleutnant]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rankInFiction
Context triple: [Der Alte, rankInFiction, Kapitänleutnant]
  • A. hasRankInFiction chosen
    Indicates that a fictional character or entity holds a specific rank, title, or hierarchical position within a fictional context or universe.
  • B. positionInFiction
    Indicates that one entity holds a specific role, status, or placement within a fictional work or narrative.
  • C. eraWithinFiction
    Indicates that a time period or era exists inside the narrative world or timeline of a fictional work.
  • D. authorshipInFiction
    Indicates that one entity is the creator or writer of a fictional work in which another entity appears or is represented.
  • E. qualityInFiction
    Indicates that a particular quality, trait, or characteristic is exhibited by an entity within a fictional context or work.
  • 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_69e0c4618bec8190bcb0feb74568cbb1 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eeeb59cee08190aae55ad6e2a4e077 completed April 27, 2026, 4:51 a.m.
PD Predicate disambiguation batch_69e6320c8c2c81908bf031447d66a052 completed April 20, 2026, 2:02 p.m.
Created at: April 16, 2026, 6:31 p.m.