Triple
T31110776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourier restriction theory |
E792937
|
entity |
| Predicate | typicalSubset |
P79471
|
FINISHED |
| Object | sphere |
—
|
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: sphere | Statement: [Fourier restriction theory, typicalSubset, sphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSubset Context triple: [Fourier restriction theory, typicalSubset, sphere]
-
A.
typicalActiveSubset
Indicates that one set is a representative or characteristic active portion of a larger set, capturing the typical elements or behavior of that larger set.
-
B.
coreSubset
chosen
Indicates that one set forms the essential or most important subset of another set, capturing its core elements.
-
C.
subset
Indicates that all elements of one set are contained within another set.
-
D.
notEverySubsetIs
Indicates that it is not the case that every subset of one set satisfies a specified relation or property with respect to another set.
-
E.
typicalSubkey
Indicates that one key is a representative or commonly occurring subkey within the context or structure of another key.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:04 p.m.