Triple
T24081682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gauss hypergeometric function |
E596519
|
entity |
| Predicate | hasBranchPoints |
P101092
|
FINISHED |
| Object | z=1 |
—
|
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: z=1 | Statement: [Gauss hypergeometric function, hasBranchPoints, z=1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBranchPoints Context triple: [Gauss hypergeometric function, hasBranchPoints, z=1]
-
A.
hasBranches
Indicates that an entity extends into multiple subordinate parts or offshoots, like limbs, divisions, or sections stemming from a main source.
-
B.
hasBranchCut
chosen
Indicates that a mathematical function possesses a branch cut, i.e., a curve or line in its domain across which the function is discontinuous or changes branch.
-
C.
hasTwoBranches
Indicates that the related entity is divided into or composed of exactly two distinct branches.
-
D.
hasBranchCharacteristic
Indicates that a branch of an entity possesses a specified characteristic or property.
-
E.
hasIslandBetweenBranches
Indicates that there is an island located in the area where the branches of something (such as a river or structure) diverge or lie between them.
- 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc24b0d081909fcae5e34c6e3b98 |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:43 p.m.