Triple
T9756953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NPF-57 |
E236576
|
entity |
| Predicate | licenseCategory |
P2182
|
FINISHED |
| Object | power reactor license |
—
|
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: power reactor license | Statement: [NPF-57, licenseCategory, power reactor license]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licenseCategory Context triple: [NPF-57, licenseCategory, power reactor license]
-
A.
licenseFamily
chosen
Indicates that one license belongs to, is derived from, or is categorized under a broader family or class of related licenses.
-
B.
licenseFocus
Indicates that a license specifically targets, applies to, or is primarily concerned with a particular subject, activity, or scope.
-
C.
licenseStatus
Indicates the current state or condition of a license in relation to its validity, permissions, or compliance.
-
D.
licenseFor
Indicates that one entity grants or holds formal permission or authorization for another entity to perform an activity, use a resource, or operate under specified conditions.
-
E.
licenseModel
Indicates the licensing scheme or framework that governs how something may be used, distributed, or accessed.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9fb2889481908fba4a449d5007fe |
completed | April 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:24 p.m.