Triple
T16931221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCLEX-PN |
E410710
|
entity |
| Predicate | testPlanUpdated |
P124793
|
FINISHED |
| Object | periodically based on practice analysis |
—
|
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: periodically based on practice analysis | Statement: [NCLEX-PN, testPlanUpdated, periodically based on practice analysis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testPlanUpdated Context triple: [NCLEX-PN, testPlanUpdated, periodically based on practice analysis]
-
A.
implementedPlan
Indicates that a specific plan has been carried out or put into effect by an entity.
-
B.
plannedNumberOfTests
Indicates the total count of tests that are intended or scheduled to be conducted for a given context or period.
-
C.
testPilot
Indicates that an entity serves as a pilot responsible for testing and evaluating aircraft or related flight systems.
-
D.
plannedUpgrade
Indicates that an entity has a scheduled or intended improvement or enhancement to be carried out in the future.
-
E.
overseesPlan
Indicates that one entity is responsible for supervising, managing, or directing the development or execution of another entity’s plan.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf25a6dc8190a2b9d9c4d2adc5fd |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e32d7aae948190bc238d765795688c |
completed | April 18, 2026, 7:06 a.m. |
Created at: April 10, 2026, 5:30 a.m.