Triple
T17020335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schauder basis |
E412930
|
entity |
| Predicate | isSequenceOf |
P125531
|
FINISHED |
| Object | vectors in a Banach space |
—
|
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: vectors in a Banach space | Statement: [Schauder basis, isSequenceOf, vectors in a Banach space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSequenceOf Context triple: [Schauder basis, isSequenceOf, vectors in a Banach space]
-
A.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
B.
hasTypeOfSequence
Indicates that one entity is characterized by or classified as a particular kind or category of sequence.
-
C.
isDigitSequence
Indicates that a given value consists solely of one or more numeric digit characters arranged in sequence.
-
D.
hasTypicalSequence
Indicates that there is a usual or commonly occurring order or progression in which the related entities or events take place.
-
E.
sequenceWith
Indicates that one entity occurs in a specific order directly before or after another entity as part of a defined sequence.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d482c3a0819099e6ea4acb0a08ee |
completed | April 18, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:33 a.m.