Triple

T12597070
Position Surface form Disambiguated ID Type / Status
Subject Dirichlet series E300759 entity
Predicate mayAdmit P105611 FINISHED
Object meromorphic continuation beyond initial half-plane 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: meromorphic continuation beyond initial half-plane | Statement: [Dirichlet series, mayAdmit, meromorphic continuation beyond initial half-plane]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayAdmit
Context triple: [Dirichlet series, mayAdmit, meromorphic continuation beyond initial half-plane]
  • A. mayAlsoAdmit
    Indicates that an entity has the option or authority to additionally allow or accept another entity, beyond any primary or default admission.
  • B. usedToAdmit
    Indicates that something served as the means or instrument by which an entity was allowed or granted entry or access.
  • C. mayPass
    Indicates that one entity is permitted or authorized to move through, cross, or gain access to another entity or location.
  • D. mayGrant
    Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
  • E. mayAdapt
    Indicates that one entity is permitted or allowed to modify, adjust, or alter another entity.
  • 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_69d7bdea2ca881908f379526c13b1145 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d954e6e20481908bca684c4b497c48 completed April 10, 2026, 7:52 p.m.
PD Predicate disambiguation batch_69d95416cbd88190b2c65196162349bc completed April 10, 2026, 7:48 p.m.
PDg Predicate description generation batch_69d954e351f88190869220d46e0ce282 completed April 10, 2026, 7:52 p.m.
Created at: April 9, 2026, 5:08 p.m.