Triple
T16218432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jessica J. Lyublanovits |
E393654
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legal administrator |
C37137
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: legal administrator Context triple: [Jessica J. Lyublanovits, instanceOf, legal administrator]
-
A.
academic administrator
An academic administrator is a professional responsible for planning, organizing, and overseeing the non-teaching operations and policies of educational institutions to support their academic mission.
-
B.
public administration position
A public administration position is a role within government or public sector organizations responsible for planning, implementing, and managing policies and services that serve the public interest.
-
C.
health benefits administrator
A health benefits administrator manages and coordinates employee health insurance and wellness programs, ensuring compliance with regulations and effective delivery of benefits.
-
D.
public benefits administrator
A public benefits administrator oversees the implementation, management, and compliance of government assistance programs to ensure eligible individuals and families receive appropriate services and support.
-
E.
academic administrative office
An academic administrative office is a centralized unit within an educational institution responsible for managing academic records, coordinating course and program logistics, supporting faculty and students with administrative processes, and ensuring compliance with institutional and regulatory policies.
- F. None of above. chosen
Provenance (1 batch)
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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:03 a.m.