Triple
T34471492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwartz space |
E884919
|
entity |
| Predicate | elementCondition |
P167326
|
FINISHED |
| Object | infinitely differentiable functions |
—
|
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: infinitely differentiable functions | Statement: [Schwartz space, elementCondition, infinitely differentiable functions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elementCondition Context triple: [Schwartz space, elementCondition, infinitely differentiable functions]
-
A.
hasElementCondition
chosen
Indicates that an entity is associated with a specific condition or set of conditions applied to one of its elements or components.
-
B.
containsCondition
Indicates that one entity includes, embodies, or is associated with a particular condition.
-
C.
edgeCondition
Indicates a condition or set of criteria that must hold at the boundary or limit of a structure, process, or domain.
-
D.
featuresCondition
Indicates that an entity includes, exhibits, or is characterized by a particular condition.
-
E.
subsetCondition
Indicates that one set or collection is entirely contained within another, satisfying a subset relationship condition.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7199e9d3881908e9427bfd02d31be |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2:01 a.m.