Triple
T25432921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurwitz theorem |
E637304
|
entity |
| Predicate | assumptionOnVariable |
P50642
|
FINISHED |
| Object | x is irrational |
—
|
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: x is irrational | Statement: [Hurwitz theorem, assumptionOnVariable, x is irrational]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assumptionOnVariable Context triple: [Hurwitz theorem, assumptionOnVariable, x is irrational]
-
A.
isAssumedIn
chosen
Indicates that something is taken for granted or presumed to hold within a particular context, without requiring explicit proof or verification.
-
B.
assumptionOnDomain
Indicates that a particular assumption or constraint is specified to hold over a given domain or set of entities.
-
C.
assumes
Indicates that one entity takes on, accepts, or presumes a role, responsibility, state, or fact regarding another entity or situation.
-
D.
assumptionTested
Indicates that an assumption or hypothesis has been subjected to a test or evaluation to verify its validity.
-
E.
assumptionOnMap
Indicates that an assumption or inferred condition is applied to, or defined over, a specific map or mapping structure.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6dc7d088190b1e4c191172ea256 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 1:58 p.m.