Triple
T4393310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compton effect |
E99416
|
entity |
| Predicate | hasMaximumShiftAt |
P4228
|
FINISHED |
| Object | scattering angle 180 degrees |
—
|
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: scattering angle 180 degrees | Statement: [Compton effect, hasMaximumShiftAt, scattering angle 180 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumShiftAt Context triple: [Compton effect, hasMaximumShiftAt, scattering angle 180 degrees]
-
A.
hasNumberOfShifts
Indicates the quantity of work shifts associated with a given entity.
-
B.
isMaximumWhen
chosen
Indicates that a quantity or function reaches its greatest possible value under specified conditions or at a particular point.
-
C.
canBeExceededIn
Indicates that one entity’s value, level, or extent is capable of being surpassed by that of another entity within a specified context.
-
D.
hasHistoricalShiftTo
Indicates a change over time in which one state, condition, or configuration is replaced or transformed into another in a historically traceable way.
-
E.
hasPeakHourService
Indicates that a service operates or is available during designated peak or high-demand hours.
- 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_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. |
Created at: March 12, 2026, 11:19 p.m.