Triple
T1390508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surreal numbers |
E29943
|
entity |
| Predicate | isClassOf |
P28232
|
FINISHED |
| Object | all numbers generated from the empty set by Conway’s rules |
—
|
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: all numbers generated from the empty set by Conway’s rules | Statement: [Surreal numbers, isClassOf, all numbers generated from the empty set by Conway’s rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClassOf Context triple: [Surreal numbers, isClassOf, all numbers generated from the empty set by Conway’s rules]
-
A.
instanceOf
relation of type constraints
-
B.
isTransitiveClass
Indicates that a class has the transitive property, meaning if it relates A to B and B to C, it must also relate A to C.
-
C.
typeOf
Indicates that one entity is a specific kind, class, or category instance of another more general entity.
-
D.
canBeTypeOf
Indicates that one entity is capable of serving as, or being classified as, a particular type or category of another entity.
-
E.
subclassOf
Indicates that one class is a more specific type of another class, inheriting its characteristics as a subset of it.
- F. None of above. chosen
Provenance (4 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c35e023c8190b45688796d90534b |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c2f16ae081908c92792253f3eb4b |
completed | March 1, 2026, 10:51 p.m. |
Created at: March 1, 2026, 7:59 p.m.