Triple
T4393309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compton effect |
E99416
|
entity |
| Predicate | occursMoreStronglyFor |
P55827
|
FINISHED |
| Object | larger scattering angles |
—
|
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: larger scattering angles | Statement: [Compton effect, occursMoreStronglyFor, larger scattering angles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursMoreStronglyFor Context triple: [Compton effect, occursMoreStronglyFor, larger scattering angles]
-
A.
strongerThan
Indicates that one entity possesses greater strength, power, or intensity than another.
-
B.
strongerDuring
Indicates that one entity exhibits greater strength or intensity than another specifically during a given time period or event.
-
C.
strengthensFrom
Indicates that one entity becomes stronger, more effective, or more intense as a result of influence, support, or input from another entity.
-
D.
isStrongerThan
Indicates that one entity possesses greater physical power, force, or effectiveness than another entity.
-
E.
strengthens
Indicates that one entity increases the power, effectiveness, or resilience of another.
- 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352a8862481909dc67abf42be6928 |
completed | March 12, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:19 p.m.