Triple
T9756964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NPF-57 |
E236576
|
entity |
| Predicate | plantDesignClass |
P90838
|
FINISHED |
| Object | BWR-4 or similar GE BWR design |
—
|
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: BWR-4 or similar GE BWR design | Statement: [NPF-57, plantDesignClass, BWR-4 or similar GE BWR design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plantDesignClass Context triple: [NPF-57, plantDesignClass, BWR-4 or similar GE BWR design]
-
A.
fieldDesign
Indicates a relationship where an entity is responsible for planning, arranging, or specifying the layout and structure of a particular field or area.
-
B.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
-
C.
wellDesignation
Indicates that an entity is assigned a specific well identifier or label, typically denoting its position or role within a well-based system (such as a plate or grid of wells).
-
D.
prototypeDesignation
Indicates that one entity is designated or identified as a prototype version or exemplar of another entity.
-
E.
plantArea
Indicates the total surface area occupied or covered by a plant or group of plants.
- 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_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. |
| PDg | Predicate description generation | batch_69cd081a9c5c819093439be7e802ff85 |
completed | April 1, 2026, 11:57 a.m. |
Created at: March 30, 2026, 8:24 p.m.