Triple
T28016116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V-320 |
E707548
|
entity |
| Predicate | enrichmentLevel |
P126133
|
FINISHED |
| Object | up to about 4.4% U-235 |
—
|
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: up to about 4.4% U-235 | Statement: [V-320, enrichmentLevel, up to about 4.4% U-235]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enrichmentLevel Context triple: [V-320, enrichmentLevel, up to about 4.4% U-235]
-
A.
enrichmentLevelRange
chosen
Indicates the range of values within which the level or degree of enrichment is considered or specified.
-
B.
enrollmentLevel
Indicates the degree or status of participation an entity has in a particular enrollment context (such as a program, course, or service).
-
C.
representationLevel
Indicates the degree or layer at which something stands in for, models, or symbolizes something else (e.g., more concrete vs. more abstract representation).
-
D.
granularityLevel
Indicates the degree of detail or resolution at which something is specified, measured, or analyzed within a given context.
-
E.
richness
Indicates that an entity possesses a high degree of abundance, complexity, or density in some valued attribute or resource.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c0796288190a5936b67d90abd00 |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:07 p.m.