Triple
T29776396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott topology |
E755389
|
entity |
| Predicate | openSetCondition |
P167867
|
FINISHED |
| Object | upper set |
—
|
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: upper set | Statement: [Scott topology, openSetCondition, upper set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openSetCondition Context triple: [Scott topology, openSetCondition, upper set]
-
A.
hasOpeningCondition
Indicates that a relationship or action is subject to a specific initial condition that must be met before it can begin or take effect.
-
B.
openStatus
Indicates whether an entity (such as a place, service, or resource) is currently open or available for use.
-
C.
isOpenTo
Indicates that one entity is receptive, willing, or available to consider, accept, or engage with another entity or proposal.
-
D.
opens
Indicates that one entity causes or allows another entity (such as an object, space, or resource) to become accessible or no longer closed.
-
E.
openedForCurrentUse
Indicates that an entity has been opened and is currently available for its intended use or operation.
- 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_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. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 28, 2026, 8:46 p.m.