Triple

T34529749
Position Surface form Disambiguated ID Type / Status
Subject Illinois attorneys E886502 entity
Predicate mustBeAdmittedTo P82580 FINISHED
Object Illinois bar 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: Illinois bar | Statement: [Illinois attorneys, mustBeAdmittedTo, Illinois bar]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mustBeAdmittedTo
Context triple: [Illinois attorneys, mustBeAdmittedTo, Illinois bar]
  • A. admissionRequired chosen
    Indicates that access to something is conditional on being formally admitted or granted entry beforehand.
  • B. mayBeAdmitted
    Indicates that an entity has the possibility or permission to be allowed entry or accepted into another entity or context.
  • C. hasAdmission
    Indicates that an entity possesses or is associated with a specific admission event, record, or status (such as being admitted to a place, program, or institution).
  • D. admittedTo
    Indicates that one entity has been formally accepted, enrolled, or granted entry into another entity, such as an institution, program, or facility.
  • E. separateAdmissionRequired
    Indicates that access to this entity or activity is not covered by a general entry and requires an additional, distinct admission or ticket.
  • 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_69f349cd7c148190aa99192b126d1527 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7234bcaa48190ac970759d34e254a completed May 3, 2026, 10:28 a.m.
PD Predicate disambiguation batch_69f72155c48881909bd40b9aa3febd5a completed May 3, 2026, 10:20 a.m.
Created at: May 1, 2026, 2:02 a.m.