Triple
T11919080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitting ideal |
E283606
|
entity |
| Predicate | isFunctorial |
P29147
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Fitting ideal, isFunctorial, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFunctorial Context triple: [Fitting ideal, isFunctorial, yes]
-
A.
functorialityProperty
chosen
Indicates that a mapping between categories preserves the structure of composition and identity morphisms, behaving consistently with the rules of a functor.
-
B.
usesFunctor
Indicates that one entity employs or applies a functor to operate on or transform another entity or structure.
-
C.
hasFaithfulCategory
Indicates that one entity is associated with a category functor that is faithful, i.e., it preserves distinct morphisms without identifying them.
-
D.
isAssociative
Indicates that the grouping of operands does not affect the result of the operation (i.e., (a * b) * c = a * (b * c)).
-
E.
isCommutative
Indicates that the result of applying an operation to two entities does not depend on their order (i.e., a ∘ b = b ∘ a).
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8dff77481908cacf6ad03df34ac |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.