Triple
T29776420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott topology |
E755389
|
entity |
| Predicate | isFinerThan |
P28230
|
FINISHED |
| Object | weak topology induced by directed suprema |
—
|
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: weak topology induced by directed suprema | Statement: [Scott topology, isFinerThan, weak topology induced by directed suprema]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFinerThan Context triple: [Scott topology, isFinerThan, weak topology induced by directed suprema]
-
A.
isCoarserThan
Indicates that one entity has a lower level of detail or granularity than another, representing a broader or less refined characterization or partition.
-
B.
isMoreSpecificThan
chosen
Indicates that one concept represents a narrower, more detailed, or more constrained case of another concept.
-
C.
isDeeperThan
Indicates that one entity has a greater depth or is positioned further down than another entity.
-
D.
containsLevel
Indicates that one entity includes or encompasses a specific level or layer within its structure or hierarchy.
-
E.
hasStricterStandardThan
Indicates that one entity’s rules, criteria, or requirements are more demanding or rigorous than those of another entity.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f674a274ac8190bfd0b8c5e021695b |
completed | May 2, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 8:46 p.m.