Triple

T33659511
Position Surface form Disambiguated ID Type / Status
Subject Paratime E862311 entity
Predicate hasFictionalLawEnforcementBody P95623 FINISHED
Object Paratime Police 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: Paratime Police | Statement: [Paratime, hasFictionalLawEnforcementBody, Paratime Police]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFictionalLawEnforcementBody
Context triple: [Paratime, hasFictionalLawEnforcementBody, Paratime Police]
  • A. hasFictionalPoliceDepartment chosen
    Indicates that an entity is associated with or features a police department that exists only within a fictional or imaginary context.
  • B. hasFictionalGovernmentAgency
    Indicates that an entity includes, features, or is associated with a government agency that is fictional rather than real.
  • C. hasPoliceInstitution
    Indicates that an entity is associated with, governed by, or served by a particular police institution or law enforcement body.
  • D. rivalFictionalAgency
    Indicates that one fictional agency stands in opposition or competition to another fictional agency.
  • E. isPartOfLawEnforcementSystem
    Indicates that an entity belongs to, operates within, or functionally contributes to a law enforcement system or framework.
  • 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_69f34984c4008190bb82f33a7819da64 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69ff409ff5548190849c2d50e99bd807 completed May 9, 2026, 2:11 p.m.
PD Predicate disambiguation batch_69ff401a5e188190a72f945e910b4a6c completed May 9, 2026, 2:09 p.m.
Created at: May 1, 2026, 1:42 a.m.