Triple
T37196765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mixed Hodge structure |
E921615
|
entity |
| Predicate | HodgeFiltrationSymbol |
P29171
|
FINISHED |
| Object | F^• |
—
|
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: F^• | Statement: [mixed Hodge structure, HodgeFiltrationSymbol, F^•]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HodgeFiltrationSymbol Context triple: [mixed Hodge structure, HodgeFiltrationSymbol, F^•]
-
A.
hasHodgeStructure
Indicates that one mathematical object is endowed with, or related to another via, a Hodge structure defining its decomposition into Hodge components.
-
B.
hasHodgeNumbers
Indicates that an entity (typically a geometric or algebraic object) is associated with specific Hodge numbers describing its Hodge decomposition or Hodge structure.
-
C.
cohomologyType
Indicates the type or classification of a cohomology theory or cohomological structure associated with an object or context.
-
D.
hasSymbolicForm
chosen
Indicates that one entity serves as the symbolic representation or abstract form of another entity.
-
E.
cohomologyRing
Indicates that one entity is the cohomology ring associated to another, encoding its cohomological structure and cup-product operations.
- 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_69f76ea313a08190a54404cd1e47da90 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.