Triple
T23301571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | residual maker matrix |
E590316
|
entity |
| Predicate | nullSpace |
P151780
|
FINISHED |
| Object | column space of X |
—
|
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: column space of X | Statement: [residual maker matrix, nullSpace, column space of X]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nullSpace Context triple: [residual maker matrix, nullSpace, column space of X]
-
A.
namedSpace
Indicates that an entity has been assigned or is associated with a specific name within a particular namespace or naming context.
-
B.
nulliusCase
Indicates that something is expressed in the genitive case used with the Latin word *nullius* (“of no one” / “of nothing”), marking a relationship of possession, origin, or association with nonexistence or absence.
-
C.
namespace
Indicates a scoping relationship in which identifiers or symbols are grouped under a specific context or name to avoid conflicts and organize them.
-
D.
N
Indicates that the entity is assigned the atomic symbol or element designation "N."
-
E.
zeroConcept
Indicates a conceptual or abstract entity that has no concrete instances or realizations in the given context.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196d37fd08190ad2d199c54324c02 |
completed | April 29, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:04 p.m.