Triple
T10829375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atiyah–Hirzebruch spectral sequence |
E255575
|
entity |
| Predicate | firstPageOften |
P76517
|
FINISHED |
| Object | E_2-page |
—
|
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: E_2-page | Statement: [Atiyah–Hirzebruch spectral sequence, firstPageOften, E_2-page]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPageOften Context triple: [Atiyah–Hirzebruch spectral sequence, firstPageOften, E_2-page]
-
A.
firstPage
chosen
Indicates that one entity is the first page or initial section in the ordered sequence of pages of another entity.
-
B.
first
Indicates that one entity precedes all others in an ordered sequence or ranking.
-
C.
firstOrdinary
Indicates that the subject is the first entity to hold or occupy an ordinary (non-special, standard) position, role, or status in a given sequence or context.
-
D.
firstStepIn
Indicates that one event, action, or process is the initial step in a larger sequence or procedure involving another.
-
E.
firstSectionOpened
Indicates that the initial section in a sequence or structure has been opened or activated.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d74420fa188190b5b3c59e1a9f551d |
completed | April 9, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.