Triple
T27077856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D.O. |
E685511
|
entity |
| Predicate | grantsQualificationAs |
P7591
|
FINISHED |
| Object | osteopathic physician |
—
|
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 physician | Statement: [D.O., grantsQualificationAs, osteopathic physician]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantsQualificationAs Context triple: [D.O., grantsQualificationAs, osteopathic physician]
-
A.
awardsQualificationTo
chosen
Indicates that one entity grants or confers a qualification, certification, or credential to another entity.
-
B.
qualifyingFor
Indicates that one entity meets the necessary conditions or criteria to be eligible for another entity, status, or action.
-
C.
hasQualification
Indicates that an entity possesses a specific qualification, credential, or competency.
-
D.
governsQualificationThrough
Indicates that one entity determines, regulates, or controls another entity’s eligibility or qualification through a specified mechanism or process.
-
E.
hasQualifying
Indicates that one entity possesses or meets a specific condition, attribute, or criterion that qualifies it in relation to another entity or context.
- 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_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 8:32 a.m.