Triple
T27077882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D.O. |
E685511
|
entity |
| Predicate | holderMayAlsoTakeExam |
P146733
|
FINISHED |
| Object | USMLE |
—
|
NE NERFINISHED |
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: USMLE | Statement: [D.O., holderMayAlsoTakeExam, USMLE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderMayAlsoTakeExam Context triple: [D.O., holderMayAlsoTakeExam, USMLE]
-
A.
writtenExamRequiredBefore
Indicates that completing a written exam is a prerequisite that must occur before another specified action or event.
-
B.
mayHoldQualification
Indicates that an entity is permitted or able to possess a particular qualification, certification, or credential.
-
C.
holderMayBe
Indicates that a particular entity is allowed or permitted to serve as the holder or possessor of another entity.
-
D.
mayTake
chosen
Indicates that an entity is permitted or allowed to take, enroll in, or participate in another entity (such as a course, resource, or opportunity).
-
E.
canEnroll
Indicates that one entity is permitted or eligible to enroll in, register for, or join another entity (such as a course, program, or service).
- 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_69f625411c14819086492062e86ba8d5 |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 8:32 a.m.