Triple
T6929719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cantor–Bernstein–Schröder theorem |
E160401
|
entity |
| Predicate | ensuresExistenceOf |
P42357
|
FINISHED |
| Object | bijection between two mutually embeddable sets |
—
|
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: bijection between two mutually embeddable sets | Statement: [Cantor–Bernstein–Schröder theorem, ensuresExistenceOf, bijection between two mutually embeddable sets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ensuresExistenceOf Context triple: [Cantor–Bernstein–Schröder theorem, ensuresExistenceOf, bijection between two mutually embeddable sets]
-
A.
existsFor
Indicates that something is present, available, or holds true for a particular entity, context, or condition.
-
B.
canExistAt
Indicates that an entity is capable of being present or occurring at a specified location, time, or context.
-
C.
existsIf
Indicates that the existence or validity of one entity or condition depends on the presence or truth of another specified condition.
-
D.
concludesExistenceOf
chosen
Indicates that one entity determines or infers that another entity exists.
-
E.
stillExists
Indicates that the referenced entity continues to exist or remain in effect at the current point in time.
- 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_69c6884e15208190b9e91487eaafcf85 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6da1f5fcc8190b43f53f90fc1821c |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bb577c81908ee8b415b4281f3d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:27 p.m.