Triple
T34471800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grothendieck ring |
E884927
|
entity |
| Predicate | additionInducedBy |
P92780
|
FINISHED |
| Object | direct sum |
—
|
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: direct sum | Statement: [Grothendieck ring, additionInducedBy, direct sum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: additionInducedBy Context triple: [Grothendieck ring, additionInducedBy, direct sum]
-
A.
inducedBy
chosen
Indicates that one entity is the cause, source, or triggering factor that brings about the existence, occurrence, or state of another entity.
-
B.
isAdditiveFor
Indicates that one entity can be combined with another in a way that their effects or quantities sum together to produce a cumulative result.
-
C.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of another entity.
-
D.
addedTo
Indicates that one entity has been included or incorporated into another entity, typically as a new component, member, or element.
-
E.
laterAdditionsBy
Indicates that one entity consists of or represents additions or modifications that were made to another entity at a later time.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7199e9d3881908e9427bfd02d31be |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2:01 a.m.