Triple
T27133737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Souslin operation |
E681625
|
entity |
| Predicate | typicalBaseClass |
P200258
|
FINISHED |
| Object | Borel 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: Borel sets | Statement: [Souslin operation, typicalBaseClass, Borel sets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBaseClass Context triple: [Souslin operation, typicalBaseClass, Borel sets]
-
A.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
-
B.
typicalFunctionClass
Indicates that something belongs to the usual or characteristic functional category associated with it.
-
C.
baseType
Indicates that one entity serves as the underlying or parent type from which another entity is derived or specialized.
-
D.
typicalInitialization
Indicates the standard or commonly used way an entity is initially set up, configured, or brought into a valid starting state.
-
E.
typicalInterface
Indicates that one entity serves as the standard or commonly used interface through which another entity is accessed or interacted with.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
| PDg | Predicate description generation | batch_69ff7dce25d88190b167a014661bc4ba |
completed | May 9, 2026, 6:32 p.m. |
Created at: April 27, 2026, 9:05 a.m.