Triple
T16787786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCLEX-RN |
E408023
|
entity |
| Predicate | scoreReportingTo |
P10741
|
FINISHED |
| Object | nursing regulatory bodies |
—
|
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: nursing regulatory bodies | Statement: [NCLEX-RN, scoreReportingTo, nursing regulatory bodies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoreReportingTo Context triple: [NCLEX-RN, scoreReportingTo, nursing regulatory bodies]
-
A.
scoreReportedTo
chosen
Indicates that a score or result has been communicated or submitted from one party to another.
-
B.
scoresWhen
Indicates that one entity achieves a score or points at the time or under the condition specified by another entity or event.
-
C.
scores
Indicates that one entity achieves or is assigned a numerical result, rating, or points in relation to another entity, such as a test, game, or evaluation.
-
D.
scoringRecord
Indicates that there exists a record documenting a scoring event or outcome associated with the given entities.
-
E.
scoreUsedFor
Indicates that a particular score or rating is used for a specific purpose, decision, or downstream process.
- 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_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. |
Created at: April 10, 2026, 5:22 a.m.