Triple
T33578950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacobian variety |
E860099
|
entity |
| Predicate | isProjective |
P176911
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Jacobian variety, isProjective, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProjective Context triple: [Jacobian variety, isProjective, true]
-
A.
isProjectiveRepresentationOf
Indicates that one mathematical object represents another up to multiplication by scalar factors, preserving structure only up to a projective (rather than strictly linear) equivalence.
-
B.
isProjectionOnto
Indicates that one entity represents the result of projecting another entity onto a specified subspace, axis, or component.
-
C.
hasProjectionSystem
Indicates that one entity uses or is defined by a particular coordinate or map projection system associated with another entity.
-
D.
isFromProject
Indicates that one entity originates from, belongs to, or was produced within a particular project.
-
E.
usesProjectionMappingOn
Indicates that one entity applies projection mapping techniques onto another entity, typically by projecting images or video content onto its surface.
- F. None of above. chosen
Provenance (4 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f70b0ca081908b24a98937e6ef66 |
completed | May 3, 2026, 7:19 a.m. |
Created at: May 1, 2026, 1:40 a.m.