Triple
T32205438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Board of Obstetrics and Gynecology |
E822655
|
entity |
| Predicate | hasExamination |
P184621
|
FINISHED |
| Object | written examination |
—
|
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: written examination | Statement: [American Board of Obstetrics and Gynecology, hasExamination, written examination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExamination Context triple: [American Board of Obstetrics and Gynecology, hasExamination, written examination]
-
A.
examinedIn
Indicates that one entity is analyzed, inspected, or studied within the context, scope, or setting provided by another entity.
-
B.
hasExaminationBranch
Indicates that an entity is associated with or conducted through a specific examination branch or division.
-
C.
hasCheckInProcedure
Indicates that there is a defined process or set of steps required for an entity to check in or be checked in.
-
D.
hasClinicalAssessment
Indicates that a subject is associated with, or has undergone, a specific clinical assessment or evaluation.
-
E.
hadProcedure
Indicates that a subject underwent or received a specific medical or clinical procedure.
- F. None of above. chosen
Provenance (4 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: May 1, 2026, 12:36 a.m.