Triple

T32621028
Position Surface form Disambiguated ID Type / Status
Subject FictionPress.com E833921 entity
Predicate hasRegistrationPolicy P203973 FINISHED
Object optional for reading — 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: optional for reading | Statement: [FictionPress.com, hasRegistrationPolicy, optional for reading]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRegistrationPolicy
Context triple: [FictionPress.com, hasRegistrationPolicy, optional for reading]
  • A. hasEnrollmentPolicy
    Indicates that there is a specific rule or set of rules governing who may enroll in, access, or participate in something and under what conditions.
  • B. hasPolicyStatus
    Indicates that an entity is associated with a policy and specifies the current status or state of that policy.
  • C. hasPolicySupport
    Indicates that one entity provides endorsement, backing, or approval for a specific policy associated with another entity.
  • D. hasRegistrationType
    Indicates that an entity is associated with a specific category or type of registration it holds or requires.
  • E. hasReferencePolicy
    Indicates that an entity is governed by or associated with a specific reference policy that defines how it should be used, accessed, or managed.
  • 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_69f3492ccc80819086ef7d26e9786647 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_6a0301c45274819083b0dd9d335f7ee0 completed May 12, 2026, 10:32 a.m.
PD Predicate disambiguation batch_6a03015c272481908a7bfe81befb1764 completed May 12, 2026, 10:30 a.m.
PDg Predicate description generation batch_6a0301c3a34c81909af5de895b1ace80 completed May 12, 2026, 10:32 a.m.
Created at: May 1, 2026, 1:06 a.m.