Triple
T27077881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D.O. |
E685511
|
entity |
| Predicate | requiresLicensingExams |
P9144
|
FINISHED |
| Object | COMLEX-USA |
—
|
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: COMLEX-USA | Statement: [D.O., requiresLicensingExams, COMLEX-USA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresLicensingExams Context triple: [D.O., requiresLicensingExams, COMLEX-USA]
-
A.
requiresCertification
Indicates that one entity can only be performed, accessed, or considered valid if another entity has an appropriate certification.
-
B.
writtenExamRequiredBefore
Indicates that completing a written exam is a prerequisite that must occur before another specified action or event.
-
C.
requiresLicenseForPractice
chosen
Indicates that engaging in the specified professional practice is legally contingent upon holding a valid license.
-
D.
requiresQualificationStandard
Indicates that performing or engaging in the referenced activity, role, or process is contingent upon meeting a specified qualification standard.
-
E.
requiresPractice
Indicates that performing or mastering one entity depends on engaging in repeated practice or training involving another entity.
- 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_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 27, 2026, 8:32 a.m.