Triple
T17181650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bremsstrahlung |
E416995
|
entity |
| Predicate | isEnhancedBy |
P39508
|
FINISHED |
| Object | high atomic number targets |
—
|
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: high atomic number targets | Statement: [Bremsstrahlung, isEnhancedBy, high atomic number targets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEnhancedBy Context triple: [Bremsstrahlung, isEnhancedBy, high atomic number targets]
-
A.
enhancedBy
chosen
Indicates that one entity’s value, effectiveness, or impact is increased or improved as a result of another entity.
-
B.
enhancesPowersOf
Indicates that one entity increases, amplifies, or strengthens the abilities or powers of another entity.
-
C.
hasBoostMechanic
Indicates that one entity (typically a game or system) includes a mechanic that temporarily increases the power, speed, or effectiveness of another entity.
-
D.
isStrongerProtectionThan
Indicates that one form of protection provides a higher level of security, defense, or safeguarding compared to another.
-
E.
isStrongerThan
Indicates that one entity possesses greater physical power, force, or effectiveness than another entity.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc1187808190aeaa0d0e6487957e |
completed | April 18, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.