Triple
T14265313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarski’s fixed point theorem |
E353628
|
entity |
| Predicate | assumptionOnFunction |
P26077
|
FINISHED |
| Object | monotone |
—
|
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: monotone | Statement: [Tarski’s fixed point theorem, assumptionOnFunction, monotone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assumptionOnFunction Context triple: [Tarski’s fixed point theorem, assumptionOnFunction, monotone]
-
A.
assumes
Indicates that one entity takes on, accepts, or presumes a role, responsibility, state, or fact regarding another entity or situation.
-
B.
assumptionOnDomain
Indicates that a particular assumption or constraint is specified to hold over a given domain or set of entities.
-
C.
assumptionOnMap
chosen
Indicates that an assumption or inferred condition is applied to, or defined over, a specific map or mapping structure.
-
D.
isAssumedIn
Indicates that something is taken for granted or presumed to hold within a particular context, without requiring explicit proof or verification.
-
E.
functionHypothesis
Indicates that an entity is proposed or assumed to serve as a function or functional explanation for another entity or phenomenon.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6357a8188190ba518a486521052b |
completed | April 14, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:09 a.m.