Triple
T21047426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindelöf space |
E518483
|
entity |
| Predicate | hasOpenCoverCondition |
P142628
|
FINISHED |
| Object | every open cover has a countable subcover |
—
|
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: every open cover has a countable subcover | Statement: [Lindelöf space, hasOpenCoverCondition, every open cover has a countable subcover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpenCoverCondition Context triple: [Lindelöf space, hasOpenCoverCondition, every open cover has a countable subcover]
-
A.
hasCoverType
Indicates that one entity possesses or is associated with a specific type or category of cover.
-
B.
containsCoverOf
Indicates that one entity includes within it a cover or covering representation of another entity.
-
C.
hasCoverFeature
Indicates that one entity serves as a prominent or featured element on the cover of another entity (such as a publication, product, or media item).
-
D.
supportsRemovableCovers
Indicates that an entity is designed to accommodate or work with covers that can be detached and reattached.
-
E.
isCoverOf
Indicates that one entity functions as a protective or enclosing layer placed over another entity.
- 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fcf4d26481908b639996500a8319 |
completed | April 21, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:34 p.m.