Triple

T23073172
Position Surface form Disambiguated ID Type / Status
Subject Councillor Krespel E575248 entity
Predicate hasFictionalProfessionOfProtagonist P34569 FINISHED
Object jurist 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: jurist | Statement: [Councillor Krespel, hasFictionalProfessionOfProtagonist, jurist]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFictionalProfessionOfProtagonist
Context triple: [Councillor Krespel, hasFictionalProfessionOfProtagonist, jurist]
  • A. hasFictionalProfessionLevel
    Indicates that an entity holds a fictional or imagined profession at a specified level, rank, or degree of expertise.
  • B. hasFictionalRole
    Indicates that an entity plays or is assigned a specific role within a fictional work or narrative.
  • C. fictionalOccupation chosen
    Indicates that one entity is the imaginary or narrative-based job, role, or profession attributed to another entity within a fictional context.
  • D. isFictionalCharacter
    Indicates that the subject is a character that exists only in fiction rather than in real life.
  • E. hasFictionalSpecialization
    Indicates that an entity’s area of focus, expertise, or role is within a fictional or imaginative domain rather than a real-world specialization.
  • 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_69e245be28d48190ad1348d5a73db37d completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18c60fa6c81908496f181c7d62033 completed April 29, 2026, 4:43 a.m.
PD Predicate disambiguation batch_69ef89e5ce748190b2c3ac3843484127 completed April 27, 2026, 4:08 p.m.
Created at: April 17, 2026, 3:56 p.m.