Triple

T24716106
Position Surface form Disambiguated ID Type / Status
Subject Enterprise Securities Market E612165 entity
Predicate requiresAdmissionDocument P63443 FINISHED
Object yes 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: yes | Statement: [Enterprise Securities Market, requiresAdmissionDocument, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresAdmissionDocument
Context triple: [Enterprise Securities Market, requiresAdmissionDocument, yes]
  • A. admissionRequired
    Indicates that access to something is conditional on being formally admitted or granted entry beforehand.
  • B. requiresDocument chosen
    Indicates that one entity can only proceed, be valid, or be completed if a specified document is provided or present.
  • C. oathOfAllegianceRequired
    Indicates that an entity is obligated to swear an oath of allegiance to another entity or authority as a condition for a status, role, or relationship.
  • D. confirmationRequirement
    Indicates that an action, decision, or change is contingent on receiving explicit confirmation from a specified party or process.
  • E. boardingRequirement
    Indicates the conditions or criteria that must be met for an entity to be allowed to board another entity (such as a vehicle, vessel, or aircraft).
  • 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_69e2d7d6e7a48190bb43b0d8bb1137a0 completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f44a417a58819081777e18dda149fd completed May 1, 2026, 6:37 a.m.
PD Predicate disambiguation batch_69f442a977b08190b44eac040cb90211 completed May 1, 2026, 6:05 a.m.
Created at: April 18, 2026, 3:36 a.m.