Triple
T4552409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardy–Littlewood maximal function |
E120395
|
entity |
| Predicate | definitionType |
P57965
|
FINISHED |
| Object | supremum of local averages |
—
|
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: supremum of local averages | Statement: [Hardy–Littlewood maximal function, definitionType, supremum of local averages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definitionType Context triple: [Hardy–Littlewood maximal function, definitionType, supremum of local averages]
-
A.
definesType
Indicates that one entity specifies or establishes the type or classification of another entity.
-
B.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
-
C.
doctrineType
Indicates that one entity is a classification or kind of doctrinal position, teaching, or belief system to which the other entity belongs or pertains.
-
D.
specType
Indicates the specific type or category of a specification that an entity is associated with.
-
E.
derivationType
Indicates the specific manner or process by which one entity is derived or obtained from another.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd581160e08190b715a8ce5c3e6c9b |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd5223423c81908317351b58cff5f5 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:09 p.m.