Triple
T1390509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surreal numbers |
E29943
|
entity |
| Predicate | hasOrderType |
P1802
|
FINISHED |
| Object | proper class length |
—
|
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: proper class length | Statement: [Surreal numbers, hasOrderType, proper class length]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrderType Context triple: [Surreal numbers, hasOrderType, proper class length]
-
A.
hasOrder
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
B.
orderType
chosen
Indicates the specific category or classification of an order, such as its purpose, channel, or processing method.
-
C.
orderTypesSupported
Indicates that a system or entity supports specific types or categories of orders that can be placed or processed.
-
D.
hasOperationType
Indicates the specific kind or category of operation associated with an entity or process.
-
E.
hasOpeningType
Indicates that one entity has, features, or is characterized by a particular type or kind of opening.
- 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_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. |
Created at: March 1, 2026, 7:59 p.m.