Triple
T4092254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lebesgue spaces |
E87728
|
entity |
| Predicate | L1Definition |
P773
|
FINISHED |
| Object | integrable 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: integrable functions | Statement: [Lebesgue spaces, L1Definition, integrable functions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: L1Definition Context triple: [Lebesgue spaces, L1Definition, integrable functions]
-
A.
laterDefinedBy
Indicates that the referenced entity’s full definition or specification is provided at a subsequent point in the same or another resource.
-
B.
localNameDefinition
Indicates that an entity’s locally scoped name is defined or specified within a particular context or namespace.
-
C.
firstDefinedBy
Indicates that one entity is the original source that formally introduced, specified, or defined another entity.
-
D.
baseDefinedBy
Indicates that something’s foundational properties, structure, or interpretation are determined or specified by a particular base or underlying system.
-
E.
defined
chosen
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefcae22a081908af65a960306b78c |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:40 p.m.