Triple
T5739484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combined Medical Services Examination |
E126577
|
entity |
| Predicate | examMode |
P52475
|
FINISHED |
| Object | computer-based test |
—
|
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: computer-based test | Statement: [Combined Medical Services Examination, examMode, computer-based test]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: examMode Context triple: [Combined Medical Services Examination, examMode, computer-based test]
-
A.
examType
chosen
Indicates the specific category or format of an exam associated with an assessment or testing event.
-
B.
examTime
Indicates the scheduled time at which an exam is to take place.
-
C.
examProvider
Indicates that one entity is the organization or individual responsible for creating, administering, or supplying an exam to another entity.
-
D.
entranceExam
Indicates that an entity is required to pass or participate in an entrance examination as a condition for admission or access to another entity.
-
E.
examCode
Indicates a relationship where a specific code uniquely identifies or is assigned to an examination or test instance.
- 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_69c0083179548190b384b0bf3c08ca4d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0255dc35c8190ab9ee5d269ce553a |
completed | March 22, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69c021c8195481909419808b002628aa |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.