Triple
T5816800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. state licensing boards |
E129005
|
entity |
| Predicate | boardMembersInclude |
P22585
|
FINISHED |
| Object | licensed professionals |
—
|
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: licensed professionals | Statement: [U.S. state licensing boards, boardMembersInclude, licensed professionals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardMembersInclude Context triple: [U.S. state licensing boards, boardMembersInclude, licensed professionals]
-
A.
boardMember
Indicates that a person serves on the governing board of an organization, participating in its oversight and decision-making.
-
B.
boardMembersRepresent
Indicates that designated board members act on behalf of, and in the interests of, a particular organization or group.
-
C.
memberEntities
chosen
Indicates that certain entities belong to, or are included as members within, a larger group or collection.
-
D.
committeeMember
Indicates that an entity serves as a member of a particular committee.
-
E.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
- 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:53 p.m.