Triple
T16787787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCLEX-RN |
E408023
|
entity |
| Predicate | passFailBasis |
P124628
|
FINISHED |
| Object | pass or fail |
—
|
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: pass or fail | Statement: [NCLEX-RN, passFailBasis, pass or fail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passFailBasis Context triple: [NCLEX-RN, passFailBasis, pass or fail]
-
A.
passes
Indicates that one entity successfully transfers, hands over, or moves something (such as an object, message, or responsibility) to another entity.
-
B.
passesUnder
Indicates that one entity moves or extends beneath another entity, typically crossing below it without direct contact.
-
C.
passType
Indicates the type or category of a pass that is involved in or assigned within the relationship between entities.
-
D.
passed
Indicates that one entity successfully transferred control, responsibility, or an item (such as an object, message, or test) to another entity or through a specified stage or condition.
-
E.
finalPassing
Indicates that an entity successfully completes or passes a final evaluation, test, or stage in a process.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b21b6a408190b0766138cc9a9ee2 |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326bac94481908c082117553320f8 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:22 a.m.