Triple
T21047127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | open mapping theorem |
E518476
|
entity |
| Predicate | statementStyle |
P25612
|
FINISHED |
| Object | global property of linear operators |
—
|
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: global property of linear operators | Statement: [open mapping theorem, statementStyle, global property of linear operators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statementStyle Context triple: [open mapping theorem, statementStyle, global property of linear operators]
-
A.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
B.
structureStyle
Indicates the architectural or design style characterizing how a structure is built or formed.
-
C.
logicStyle
Indicates how an entity’s reasoning, argumentation, or inference process is structured or conducted.
-
D.
syntaxStyle
chosen
Indicates the stylistic or structural conventions used in the form or arrangement of an expression, statement, or code.
-
E.
passingStyle
Indicates the manner or technique by which something (typically a ball or object) is passed from one entity to another.
- 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fcf4d26481908b639996500a8319 |
completed | April 21, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:34 p.m.