Triple
T25073711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euler class |
E627991
|
entity |
| Predicate | functorialUnder |
P29147
|
FINISHED |
| Object | pullback of bundles |
—
|
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: pullback of bundles | Statement: [Euler class, functorialUnder, pullback of bundles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functorialUnder Context triple: [Euler class, functorialUnder, pullback of bundles]
-
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.
associatedFunctor
Indicates that one entity is functionally or conceptually linked to another entity that serves as its corresponding functor.
-
C.
invariantUnder
Indicates that a property, structure, or quantity remains unchanged when a specified transformation or operation is applied.
-
D.
transformsUnder
Indicates a relationship where one entity changes form, state, or structure when subjected to the influence, conditions, or operation specified by another entity.
-
E.
usesFunctor
Indicates that one entity employs or applies a functor to operate on or transform another entity or structure.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46d3f35848190b56a4373c97a7d64 |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 6:20 a.m.