Triple
T36469487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green’s conjecture |
E898503
|
entity |
| Predicate | formulationUses |
P96516
|
FINISHED |
| Object | Koszul cohomology |
—
|
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: Koszul cohomology | Statement: [Green’s conjecture, formulationUses, Koszul cohomology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formulationUses Context triple: [Green’s conjecture, formulationUses, Koszul cohomology]
-
A.
coFormulatedWith
Indicates that one entity is formulated together with another as part of the same combined product or composition.
-
B.
formulatedIn
Indicates that something was created, developed, or expressed within a particular context, place, or framework.
-
C.
isFormulatedUsing
chosen
Indicates that something is created, defined, or expressed by means of a specified method, material, or set of components.
-
D.
formulationFeature
Indicates a relationship where a formulation possesses, includes, or is characterized by a particular feature or property.
-
E.
activeIngredientOf
Indicates that one entity is the pharmacologically active component contained within or responsible for the primary effect of another entity, such as a drug or product.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.