Triple
T23372517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SL(n,ℝ) |
E593510
|
entity |
| Predicate | hasRealStructureConstants |
P152479
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [SL(n,ℝ), hasRealStructureConstants, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRealStructureConstants Context triple: [SL(n,ℝ), hasRealStructureConstants, true]
-
A.
hasRealStructure
Indicates that an abstract object or system is endowed with a concrete, well-defined mathematical or physical structure that makes it realizable or interpretable in a real-world or formal model.
-
B.
hasManifoldStructure
Indicates that one entity endows or possesses a manifold structure on or over another entity.
-
C.
hasRealEmbeddings
Indicates that an entity is represented or can be represented using real-valued vector embeddings in some vector space.
-
D.
hasRealComponents
Indicates that an entity possesses components or parts whose values are real (non-complex) numbers.
-
E.
hasHodgeStructure
Indicates that one mathematical object is endowed with, or related to another via, a Hodge structure defining its decomposition into Hodge components.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3af45ec8190a32aa4e5f04f6756 |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 5:32 p.m.