Triple
T34154978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beilinson spectral sequence |
E876107
|
entity |
| Predicate | typicalBaseField |
P205341
|
FINISHED |
| Object | algebraically closed field |
—
|
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: algebraically closed field | Statement: [Beilinson spectral sequence, typicalBaseField, algebraically closed field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBaseField Context triple: [Beilinson spectral sequence, typicalBaseField, algebraically closed field]
-
A.
typicalFields
Indicates the standard or commonly occurring attributes or data fields that are usually associated with an entity or record.
-
B.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
-
C.
typicalEntryType
Indicates the usual or standard category or kind of entry associated with something.
-
D.
baseType
Indicates that one entity serves as the underlying or parent type from which another entity is derived or specialized.
-
E.
typicalProperty
Indicates that a certain property is characteristically or commonly associated with an entity, reflecting what is typical for that entity.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:54 a.m.