Triple
T27077897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D.O. |
E685511
|
entity |
| Predicate | regulatoryBodyType |
P123431
|
FINISHED |
| Object | osteopathic medical boards |
—
|
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: osteopathic medical boards | Statement: [D.O., regulatoryBodyType, osteopathic medical boards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatoryBodyType Context triple: [D.O., regulatoryBodyType, osteopathic medical boards]
-
A.
typeOfComplianceBody
chosen
Indicates that one entity is a compliance-related body or authority of the type specified by the other entity.
-
B.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
C.
typeOfAgencyRegulated
Indicates that one entity is the kind or category of agency that is subject to regulation by another entity.
-
D.
hasRegulatoryOrCulturalBody
Indicates that an entity is overseen, guided, or influenced by a formal regulatory authority or a culturally significant governing body.
-
E.
createsRegulatoryBody
Indicates that an entity establishes or brings into existence an official regulatory authority responsible for overseeing and enforcing rules in a specific domain.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 8:32 a.m.