Triple
T35183989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Low’s theorem |
E1015932
|
entity |
| Predicate | isValidIn |
P9768
|
FINISHED |
| Object | on‑shell scattering processes |
—
|
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: on‑shell scattering processes | Statement: [Low’s theorem, isValidIn, on‑shell scattering processes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isValidIn Context triple: [Low’s theorem, isValidIn, on‑shell scattering processes]
-
A.
validIn
chosen
Indicates that a given entity, statement, or condition is applicable, correct, or legally/semantically acceptable within a specified context, scope, or domain.
-
B.
hasValidity
Indicates that something possesses a period or condition during which it is considered legally, logically, or functionally acceptable or in force.
-
C.
validInLimit
Indicates that a condition, rule, or value remains applicable or holds true as some parameter approaches a specified limit or boundary.
-
D.
validityType
Indicates the specific kind or category of validity that characterizes how or under what conditions something is considered valid.
-
E.
upholdsValidityOf
Indicates that one entity confirms, supports, or maintains the correctness and legitimacy of 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dbf72648190a4971a558e9d1889 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.