Triple
T27133633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borel set |
E681623
|
entity |
| Predicate | specialCaseOn |
P7025
|
FINISHED |
| Object | real line ℝ with standard topology |
—
|
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: real line ℝ with standard topology | Statement: [Borel set, specialCaseOn, real line ℝ with standard topology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialCaseOn Context triple: [Borel set, specialCaseOn, real line ℝ with standard topology]
-
A.
specialCaseOf
chosen
Indicates that one entity represents a more specific, exceptional, or restricted instance of the general situation, rule, or relationship expressed by another entity.
-
B.
specialCaseParameter
Indicates that a parameter is used only in specific or exceptional cases, differing from the standard or default behavior.
-
C.
specialValue
Indicates that an entity possesses a distinguished or exceptional value compared to typical or default values in the given context.
-
D.
specialAppearance
Indicates that an entity makes a notable or exceptional appearance distinct from its usual or regular presence.
-
E.
caseTypeSpecialization
Indicates that one case type is a more specific or specialized subtype of another, more general case type.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 9:05 a.m.