Triple
T34154970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beilinson spectral sequence |
E876107
|
entity |
| Predicate | relatedToSpace |
P37
|
FINISHED |
| Object | projective space P^n |
—
|
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: projective space P^n | Statement: [Beilinson spectral sequence, relatedToSpace, projective space P^n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToSpace Context triple: [Beilinson spectral sequence, relatedToSpace, projective space P^n]
-
A.
associatedSpacetime
Indicates a relationship where an entity is linked to, or situated within, a particular spacetime region or context.
-
B.
associatedWithSpacecraft
Indicates a relationship in which an entity is connected or related in some way to a particular spacecraft, such as by operation, design, mission, or support role.
-
C.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
D.
belongsToSpaceProgram
Indicates that an entity is part of, affiliated with, or under the authority of a specific space program.
-
E.
relatedToFeature
Indicates that there is a general association or connection between an entity and a particular feature.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:54 a.m.